=> Bootstrap dependency digest>=20211023: found digest-20220214 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Building for py312-mezzanine-6.0.0 * Building wheel... running bdist_wheel /usr/pkg/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:124: SetuptoolsDeprecationWarning: bdist_wheel.universal is deprecated !! ******************************************************************************** With Python 2.7 end-of-life, support for building universal wheels (i.e., wheels that support both Python 2 and Python 3) is being obviated. Please discontinue using this option, or if you still need it, file an issue with pypa/setuptools describing your use case. By 2025-Aug-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! self.finalize_options() running build running build_py creating build/lib/mezzanine copying mezzanine/__init__.py -> build/lib/mezzanine copying mezzanine/urls.py -> build/lib/mezzanine running egg_info writing Mezzanine.egg-info/PKG-INFO writing dependency_links to Mezzanine.egg-info/dependency_links.txt writing entry points to Mezzanine.egg-info/entry_points.txt writing requirements to Mezzanine.egg-info/requires.txt writing top-level names to Mezzanine.egg-info/top_level.txt reading manifest file 'Mezzanine.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*' found under directory 'docs/build' warning: no previously-included files matching '*' found under directory '*/project_template/static' warning: no previously-included files matching '__pycache__' found anywhere in distribution warning: no previously-included files matching '*.py[co]' found anywhere in distribution no previously-included directories found matching '.tx' no previously-included directories found matching 'tests' warning: no previously-included files found matching '.releaserc' warning: no previously-included files found matching '.isort.cfg' warning: no previously-included files found matching 'tox.ini' warning: no previously-included files found matching 'pytest.ini' warning: no previously-included files found matching '.coveragerc' adding license file 'LICENSE' writing manifest file 'Mezzanine.egg-info/SOURCES.txt' /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts' to be distributed and are already explicitly excluding 'mezzanine.accounts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.hr_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 'mezzanine.accounts.locale.hr_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 'mezzanine.accounts.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.id_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 'mezzanine.accounts.locale.id_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 'mezzanine.accounts.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.accounts.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.templates.accounts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.templates.accounts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.templates.accounts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.templates.accounts' to be distributed and are already explicitly excluding 'mezzanine.accounts.templates.accounts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.templates.accounts.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.templates.accounts.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.templates.accounts.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.templates.accounts.includes' to be distributed and are already explicitly excluding 'mezzanine.accounts.templates.accounts.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.templates.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.templates.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 'mezzanine.accounts.templates.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 'mezzanine.accounts.templates.admin' to be distributed and are already explicitly excluding 'mezzanine.accounts.templates.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.templates.email' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.templates.email' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.accounts.templates.email' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.accounts.templates.email' to be distributed and are already explicitly excluding 'mezzanine.accounts.templates.email' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.accounts.templatetags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.accounts.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 'mezzanine.accounts.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 'mezzanine.accounts.templatetags' to be distributed and are already explicitly excluding 'mezzanine.accounts.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.bin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.bin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.bin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.bin' to be distributed and are already explicitly excluding 'mezzanine.bin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.bin.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.bin.management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.bin.management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.bin.management' to be distributed and are already explicitly excluding 'mezzanine.bin.management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.bin.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.bin.management.commands' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.bin.management.commands' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.bin.management.commands' to be distributed and are already explicitly excluding 'mezzanine.bin.management.commands' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog' to be distributed and are already explicitly excluding 'mezzanine.blog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.hr_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 'mezzanine.blog.locale.hr_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 'mezzanine.blog.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.id_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 'mezzanine.blog.locale.id_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 'mezzanine.blog.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.blog.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.management' to be distributed and are already explicitly excluding 'mezzanine.blog.management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.management.commands' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.management.commands' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.management.commands' to be distributed and are already explicitly excluding 'mezzanine.blog.management.commands' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.migrations' to be distributed and are already explicitly excluding 'mezzanine.blog.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.templates.admin.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.templates.admin.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.templates.admin.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.templates.admin.includes' to be distributed and are already explicitly excluding 'mezzanine.blog.templates.admin.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.templates.blog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.templates.blog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.templates.blog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.templates.blog' to be distributed and are already explicitly excluding 'mezzanine.blog.templates.blog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.templates.blog.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.templates.blog.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.blog.templates.blog.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.blog.templates.blog.includes' to be distributed and are already explicitly excluding 'mezzanine.blog.templates.blog.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.blog.templatetags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.blog.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 'mezzanine.blog.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 'mezzanine.blog.templatetags' to be distributed and are already explicitly excluding 'mezzanine.blog.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.boot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.boot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.boot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.boot' to be distributed and are already explicitly excluding 'mezzanine.boot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf' to be distributed and are already explicitly excluding 'mezzanine.conf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.hr_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 'mezzanine.conf.locale.hr_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 'mezzanine.conf.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.id_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 'mezzanine.conf.locale.id_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 'mezzanine.conf.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.conf.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.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 'mezzanine.conf.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 'mezzanine.conf.migrations' to be distributed and are already explicitly excluding 'mezzanine.conf.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.static.mezzanine.css.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.static.mezzanine.css.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 'mezzanine.conf.static.mezzanine.css.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 'mezzanine.conf.static.mezzanine.css.admin' to be distributed and are already explicitly excluding 'mezzanine.conf.static.mezzanine.css.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.static.mezzanine.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.static.mezzanine.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.static.mezzanine.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.static.mezzanine.js.admin' to be distributed and are already explicitly excluding 'mezzanine.conf.static.mezzanine.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.conf.templates.admin.conf.setting' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.conf.templates.admin.conf.setting' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.conf.templates.admin.conf.setting' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.conf.templates.admin.conf.setting' to be distributed and are already explicitly excluding 'mezzanine.conf.templates.admin.conf.setting' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core' to be distributed and are already explicitly excluding 'mezzanine.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.hr_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 'mezzanine.core.locale.hr_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 'mezzanine.core.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.id_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 'mezzanine.core.locale.id_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 'mezzanine.core.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.core.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.management' to be distributed and are already explicitly excluding 'mezzanine.core.management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.management.commands' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.management.commands' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.management.commands' to be distributed and are already explicitly excluding 'mezzanine.core.management.commands' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.migrations' to be distributed and are already explicitly excluding 'mezzanine.core.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static' to be distributed and are already explicitly excluding 'mezzanine.core.static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.admin.img.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.admin.img.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 'mezzanine.core.static.admin.img.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 'mezzanine.core.static.admin.img.admin' to be distributed and are already explicitly excluding 'mezzanine.core.static.admin.img.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.admin.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.admin.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.admin.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.admin.js' to be distributed and are already explicitly excluding 'mezzanine.core.static.admin.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.css' to be distributed and are already explicitly excluding 'mezzanine.core.static.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.fonts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.fonts' to be distributed and are already explicitly excluding 'mezzanine.core.static.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.img' to be distributed and are already explicitly excluding 'mezzanine.core.static.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.js' to be distributed and are already explicitly excluding 'mezzanine.core.static.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.chosen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.chosen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.chosen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.chosen' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.chosen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.css' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.css.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.css.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 'mezzanine.core.static.mezzanine.css.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 'mezzanine.core.static.mezzanine.css.admin' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.css.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.css.smoothness' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.css.smoothness' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.css.smoothness' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.css.smoothness' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.css.smoothness' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.css.smoothness.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.css.smoothness.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.css.smoothness.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.css.smoothness.images' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.css.smoothness.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.img' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.js' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.js.admin' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.langs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.langs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.langs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.langs' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.langs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.advlist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.advlist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.advlist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.advlist' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.advlist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.anchor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.anchor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.anchor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.anchor' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.anchor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.autolink' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.autolink' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.autolink' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.autolink' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.autolink' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.autoresize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.autoresize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.autoresize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.autoresize' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.autoresize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.autosave' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.autosave' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.autosave' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.autosave' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.autosave' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.bbcode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.bbcode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.bbcode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.bbcode' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.bbcode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.charmap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.charmap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.charmap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.charmap' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.charmap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.code' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.code' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.code' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.code' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.code' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.colorpicker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.colorpicker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.colorpicker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.colorpicker' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.colorpicker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.contextmenu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.contextmenu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.contextmenu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.contextmenu' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.contextmenu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.directionality' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.directionality' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.directionality' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.directionality' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.directionality' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons.img' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.emoticons.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.example' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.example' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.example' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.example' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.example' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.example_dependency' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.example_dependency' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.example_dependency' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.example_dependency' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.example_dependency' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.fullpage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.fullpage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.fullpage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.fullpage' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.fullpage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.fullscreen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.fullscreen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.fullscreen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.fullscreen' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.fullscreen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.hr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.hr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.hr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.hr' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.hr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.image' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.imagetools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.imagetools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.imagetools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.imagetools' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.imagetools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.importcss' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.importcss' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.importcss' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.importcss' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.importcss' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.insertdatetime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.insertdatetime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.insertdatetime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.insertdatetime' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.insertdatetime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.layer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.layer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.layer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.layer' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.layer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.legacyoutput' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.legacyoutput' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.legacyoutput' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.legacyoutput' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.legacyoutput' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.link' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.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 'mezzanine.core.static.mezzanine.tinymce.plugins.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 'mezzanine.core.static.mezzanine.tinymce.plugins.link' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.lists' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.media' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.media' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.media' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.media' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.media' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.nonbreaking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.nonbreaking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.nonbreaking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.nonbreaking' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.nonbreaking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.noneditable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.noneditable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.noneditable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.noneditable' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.noneditable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.pagebreak' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.pagebreak' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.pagebreak' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.pagebreak' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.pagebreak' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.paste' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.paste' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.paste' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.paste' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.paste' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.preview' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.preview' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.preview' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.preview' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.preview' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.print' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.print' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.print' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.print' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.print' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.save' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.save' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.save' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.save' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.save' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.searchreplace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.searchreplace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.searchreplace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.searchreplace' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.searchreplace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.spellchecker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.spellchecker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.spellchecker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.spellchecker' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.spellchecker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.tabfocus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.tabfocus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.tabfocus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.tabfocus' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.tabfocus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.table' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.table' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.table' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.table' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.table' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.template' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.textcolor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.textcolor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.textcolor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.textcolor' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.textcolor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.textpattern' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.textpattern' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.textpattern' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.textpattern' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.textpattern' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks.css' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.visualblocks.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.visualchars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.visualchars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.visualchars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.visualchars' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.visualchars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.plugins.wordcount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.plugins.wordcount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.plugins.wordcount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.plugins.wordcount' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.plugins.wordcount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.fonts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.fonts' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.img' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.skins.lightgray.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.mezzanine.tinymce.themes.modern' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.mezzanine.tinymce.themes.modern' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.mezzanine.tinymce.themes.modern' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.mezzanine.tinymce.themes.modern' to be distributed and are already explicitly excluding 'mezzanine.core.static.mezzanine.tinymce.themes.modern' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.static.test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.static.test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.static.test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.static.test' to be distributed and are already explicitly excluding 'mezzanine.core.static.test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.templates' to be distributed and are already explicitly excluding 'mezzanine.core.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templates.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.templates.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 'mezzanine.core.templates.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 'mezzanine.core.templates.admin' to be distributed and are already explicitly excluding 'mezzanine.core.templates.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templates.admin.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.templates.admin.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.templates.admin.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.templates.admin.includes' to be distributed and are already explicitly excluding 'mezzanine.core.templates.admin.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templates.email' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.templates.email' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.templates.email' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.templates.email' to be distributed and are already explicitly excluding 'mezzanine.core.templates.email' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templates.errors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.templates.errors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.templates.errors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.templates.errors' to be distributed and are already explicitly excluding 'mezzanine.core.templates.errors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templates.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.templates.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.core.templates.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.core.templates.includes' to be distributed and are already explicitly excluding 'mezzanine.core.templates.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.core.templatetags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.core.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 'mezzanine.core.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 'mezzanine.core.templatetags' to be distributed and are already explicitly excluding 'mezzanine.core.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms' to be distributed and are already explicitly excluding 'mezzanine.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.fixtures' to be distributed and are already explicitly excluding 'mezzanine.forms.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.hr_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 'mezzanine.forms.locale.hr_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 'mezzanine.forms.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.id_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 'mezzanine.forms.locale.id_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 'mezzanine.forms.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.forms.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.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 'mezzanine.forms.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 'mezzanine.forms.migrations' to be distributed and are already explicitly excluding 'mezzanine.forms.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.static.mezzanine.css.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.static.mezzanine.css.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 'mezzanine.forms.static.mezzanine.css.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 'mezzanine.forms.static.mezzanine.css.admin' to be distributed and are already explicitly excluding 'mezzanine.forms.static.mezzanine.css.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.static.mezzanine.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.static.mezzanine.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.static.mezzanine.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.static.mezzanine.js.admin' to be distributed and are already explicitly excluding 'mezzanine.forms.static.mezzanine.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.templates.admin.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.templates.admin.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.templates.admin.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.templates.admin.forms' to be distributed and are already explicitly excluding 'mezzanine.forms.templates.admin.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.templates.email' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.templates.email' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.templates.email' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.templates.email' to be distributed and are already explicitly excluding 'mezzanine.forms.templates.email' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.forms.templates.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.forms.templates.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.forms.templates.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.forms.templates.pages' to be distributed and are already explicitly excluding 'mezzanine.forms.templates.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries' to be distributed and are already explicitly excluding 'mezzanine.galleries' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.fixtures' to be distributed and are already explicitly excluding 'mezzanine.galleries.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.hr_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 'mezzanine.galleries.locale.hr_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 'mezzanine.galleries.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.id_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 'mezzanine.galleries.locale.id_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 'mezzanine.galleries.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.galleries.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.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 'mezzanine.galleries.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 'mezzanine.galleries.migrations' to be distributed and are already explicitly excluding 'mezzanine.galleries.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.static.mezzanine.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.static.mezzanine.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.static.mezzanine.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.static.mezzanine.css' to be distributed and are already explicitly excluding 'mezzanine.galleries.static.mezzanine.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.static.mezzanine.css.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.static.mezzanine.css.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 'mezzanine.galleries.static.mezzanine.css.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 'mezzanine.galleries.static.mezzanine.css.admin' to be distributed and are already explicitly excluding 'mezzanine.galleries.static.mezzanine.css.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.static.mezzanine.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.static.mezzanine.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.static.mezzanine.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.static.mezzanine.js' to be distributed and are already explicitly excluding 'mezzanine.galleries.static.mezzanine.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.galleries.templates.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.galleries.templates.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.galleries.templates.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.galleries.templates.pages' to be distributed and are already explicitly excluding 'mezzanine.galleries.templates.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic' to be distributed and are already explicitly excluding 'mezzanine.generic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.hr_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 'mezzanine.generic.locale.hr_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 'mezzanine.generic.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.id_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 'mezzanine.generic.locale.id_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 'mezzanine.generic.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.generic.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.migrations' to be distributed and are already explicitly excluding 'mezzanine.generic.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.templates.admin.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.templates.admin.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.templates.admin.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.templates.admin.includes' to be distributed and are already explicitly excluding 'mezzanine.generic.templates.admin.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.templates.email' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.templates.email' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.templates.email' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.templates.email' to be distributed and are already explicitly excluding 'mezzanine.generic.templates.email' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.templates.generic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.templates.generic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.templates.generic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.templates.generic' to be distributed and are already explicitly excluding 'mezzanine.generic.templates.generic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.templates.generic.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.templates.generic.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.generic.templates.generic.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.generic.templates.generic.includes' to be distributed and are already explicitly excluding 'mezzanine.generic.templates.generic.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.generic.templatetags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.generic.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 'mezzanine.generic.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 'mezzanine.generic.templatetags' to be distributed and are already explicitly excluding 'mezzanine.generic.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.mobile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.mobile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.mobile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.mobile' to be distributed and are already explicitly excluding 'mezzanine.mobile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages' to be distributed and are already explicitly excluding 'mezzanine.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.fixtures' to be distributed and are already explicitly excluding 'mezzanine.pages.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.hr_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 'mezzanine.pages.locale.hr_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 'mezzanine.pages.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.id_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 'mezzanine.pages.locale.id_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 'mezzanine.pages.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.pages.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.migrations' to be distributed and are already explicitly excluding 'mezzanine.pages.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.static.mezzanine.css.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.static.mezzanine.css.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 'mezzanine.pages.static.mezzanine.css.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 'mezzanine.pages.static.mezzanine.css.admin' to be distributed and are already explicitly excluding 'mezzanine.pages.static.mezzanine.css.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.static.mezzanine.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.static.mezzanine.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.static.mezzanine.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.static.mezzanine.js.admin' to be distributed and are already explicitly excluding 'mezzanine.pages.static.mezzanine.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.templates.admin.pages.link' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.templates.admin.pages.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 'mezzanine.pages.templates.admin.pages.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 'mezzanine.pages.templates.admin.pages.link' to be distributed and are already explicitly excluding 'mezzanine.pages.templates.admin.pages.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.templates.admin.pages.page' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.templates.admin.pages.page' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.templates.admin.pages.page' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.templates.admin.pages.page' to be distributed and are already explicitly excluding 'mezzanine.pages.templates.admin.pages.page' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.templates.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.templates.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.templates.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.templates.pages' to be distributed and are already explicitly excluding 'mezzanine.pages.templates.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.templates.pages.menus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.templates.pages.menus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.pages.templates.pages.menus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.pages.templates.pages.menus' to be distributed and are already explicitly excluding 'mezzanine.pages.templates.pages.menus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.pages.templatetags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.pages.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 'mezzanine.pages.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 'mezzanine.pages.templatetags' to be distributed and are already explicitly excluding 'mezzanine.pages.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.project_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.project_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.project_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.project_template' to be distributed and are already explicitly excluding 'mezzanine.project_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.project_template.project_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.project_template.project_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.project_template.project_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.project_template.project_name' to be distributed and are already explicitly excluding 'mezzanine.project_template.project_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.template' to be distributed and are already explicitly excluding 'mezzanine.template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.template.loaders' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.template.loaders' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.template.loaders' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.template.loaders' to be distributed and are already explicitly excluding 'mezzanine.template.loaders' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter' to be distributed and are already explicitly excluding 'mezzanine.twitter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.hr_HR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.hr_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 'mezzanine.twitter.locale.hr_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 'mezzanine.twitter.locale.hr_HR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.hr_HR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.id_ID.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.id_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 'mezzanine.twitter.locale.id_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 'mezzanine.twitter.locale.id_ID.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.id_ID.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'mezzanine.twitter.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.management' to be distributed and are already explicitly excluding 'mezzanine.twitter.management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.management.commands' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.management.commands' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.management.commands' to be distributed and are already explicitly excluding 'mezzanine.twitter.management.commands' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.migrations' to be distributed and are already explicitly excluding 'mezzanine.twitter.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.templates.twitter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.templates.twitter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.twitter.templates.twitter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.twitter.templates.twitter' to be distributed and are already explicitly excluding 'mezzanine.twitter.templates.twitter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.twitter.templatetags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.twitter.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 'mezzanine.twitter.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 'mezzanine.twitter.templatetags' to be distributed and are already explicitly excluding 'mezzanine.twitter.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) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'mezzanine.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'mezzanine.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'mezzanine.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'mezzanine.utils' to be distributed and are already explicitly excluding 'mezzanine.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/mezzanine/accounts copying mezzanine/accounts/__init__.py -> build/lib/mezzanine/accounts copying mezzanine/accounts/admin.py -> build/lib/mezzanine/accounts copying mezzanine/accounts/defaults.py -> build/lib/mezzanine/accounts copying mezzanine/accounts/forms.py -> build/lib/mezzanine/accounts copying mezzanine/accounts/models.py -> build/lib/mezzanine/accounts copying mezzanine/accounts/urls.py -> build/lib/mezzanine/accounts copying mezzanine/accounts/views.py -> build/lib/mezzanine/accounts creating build/lib/mezzanine/accounts/locale/ar/LC_MESSAGES copying mezzanine/accounts/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/ar/LC_MESSAGES copying mezzanine/accounts/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/ar/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/bg/LC_MESSAGES copying mezzanine/accounts/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/bg/LC_MESSAGES copying mezzanine/accounts/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/bg/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/ca/LC_MESSAGES copying mezzanine/accounts/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/ca/LC_MESSAGES copying mezzanine/accounts/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/ca/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/cs/LC_MESSAGES copying mezzanine/accounts/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/cs/LC_MESSAGES copying mezzanine/accounts/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/cs/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/da/LC_MESSAGES copying mezzanine/accounts/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/da/LC_MESSAGES copying mezzanine/accounts/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/da/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/de/LC_MESSAGES copying mezzanine/accounts/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/de/LC_MESSAGES copying mezzanine/accounts/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/de/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/en/LC_MESSAGES copying mezzanine/accounts/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/en/LC_MESSAGES copying mezzanine/accounts/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/en/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/eo/LC_MESSAGES copying mezzanine/accounts/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/eo/LC_MESSAGES copying mezzanine/accounts/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/eo/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/es/LC_MESSAGES copying mezzanine/accounts/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/es/LC_MESSAGES copying mezzanine/accounts/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/es/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/et/LC_MESSAGES copying mezzanine/accounts/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/et/LC_MESSAGES copying mezzanine/accounts/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/et/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/fa/LC_MESSAGES copying mezzanine/accounts/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/fa/LC_MESSAGES copying mezzanine/accounts/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/fa/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/fa_IR/LC_MESSAGES copying mezzanine/accounts/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/fa_IR/LC_MESSAGES copying mezzanine/accounts/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/fi/LC_MESSAGES copying mezzanine/accounts/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/fi/LC_MESSAGES copying mezzanine/accounts/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/fi/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/fr/LC_MESSAGES copying mezzanine/accounts/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/fr/LC_MESSAGES copying mezzanine/accounts/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/fr/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/hr_HR/LC_MESSAGES copying mezzanine/accounts/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/hr_HR/LC_MESSAGES copying mezzanine/accounts/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/hu/LC_MESSAGES copying mezzanine/accounts/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/hu/LC_MESSAGES copying mezzanine/accounts/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/hu/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/id_ID/LC_MESSAGES copying mezzanine/accounts/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/id_ID/LC_MESSAGES copying mezzanine/accounts/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/is_IS/LC_MESSAGES copying mezzanine/accounts/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/is_IS/LC_MESSAGES copying mezzanine/accounts/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/it/LC_MESSAGES copying mezzanine/accounts/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/it/LC_MESSAGES copying mezzanine/accounts/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/it/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/ja/LC_MESSAGES copying mezzanine/accounts/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/ja/LC_MESSAGES copying mezzanine/accounts/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/ja/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/ko/LC_MESSAGES copying mezzanine/accounts/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/ko/LC_MESSAGES copying mezzanine/accounts/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/ko/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/lv/LC_MESSAGES copying mezzanine/accounts/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/lv/LC_MESSAGES copying mezzanine/accounts/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/lv/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/nb/LC_MESSAGES copying mezzanine/accounts/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/nb/LC_MESSAGES copying mezzanine/accounts/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/nb/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/nl/LC_MESSAGES copying mezzanine/accounts/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/nl/LC_MESSAGES copying mezzanine/accounts/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/nl/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/pap/LC_MESSAGES copying mezzanine/accounts/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/pap/LC_MESSAGES copying mezzanine/accounts/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/pap/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/pl/LC_MESSAGES copying mezzanine/accounts/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/pl/LC_MESSAGES copying mezzanine/accounts/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/pl/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/pt_BR/LC_MESSAGES copying mezzanine/accounts/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/pt_BR/LC_MESSAGES copying mezzanine/accounts/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/pt_PT/LC_MESSAGES copying mezzanine/accounts/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/pt_PT/LC_MESSAGES copying mezzanine/accounts/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/ru/LC_MESSAGES copying mezzanine/accounts/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/ru/LC_MESSAGES copying mezzanine/accounts/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/ru/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/sk/LC_MESSAGES copying mezzanine/accounts/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/sk/LC_MESSAGES copying mezzanine/accounts/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/sk/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/sr_Latn/LC_MESSAGES copying mezzanine/accounts/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/sr_Latn/LC_MESSAGES copying mezzanine/accounts/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/sv/LC_MESSAGES copying mezzanine/accounts/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/sv/LC_MESSAGES copying mezzanine/accounts/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/sv/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/tr/LC_MESSAGES copying mezzanine/accounts/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/tr/LC_MESSAGES copying mezzanine/accounts/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/tr/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/uk_UA/LC_MESSAGES copying mezzanine/accounts/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/uk_UA/LC_MESSAGES copying mezzanine/accounts/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/vi_VN/LC_MESSAGES copying mezzanine/accounts/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/vi_VN/LC_MESSAGES copying mezzanine/accounts/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/zh/LC_MESSAGES copying mezzanine/accounts/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/zh/LC_MESSAGES copying mezzanine/accounts/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/zh/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/zh_CN/LC_MESSAGES copying mezzanine/accounts/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/zh_CN/LC_MESSAGES copying mezzanine/accounts/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/accounts/locale/zh_TW/LC_MESSAGES copying mezzanine/accounts/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/accounts/locale/zh_TW/LC_MESSAGES copying mezzanine/accounts/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/accounts/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/accounts/templates/accounts copying mezzanine/accounts/templates/accounts/account_form.html -> build/lib/mezzanine/accounts/templates/accounts copying mezzanine/accounts/templates/accounts/account_login.html -> build/lib/mezzanine/accounts/templates/accounts copying mezzanine/accounts/templates/accounts/account_password_reset.html -> build/lib/mezzanine/accounts/templates/accounts copying mezzanine/accounts/templates/accounts/account_profile.html -> build/lib/mezzanine/accounts/templates/accounts copying mezzanine/accounts/templates/accounts/account_profile_update.html -> build/lib/mezzanine/accounts/templates/accounts copying mezzanine/accounts/templates/accounts/account_signup.html -> build/lib/mezzanine/accounts/templates/accounts creating build/lib/mezzanine/accounts/templates/accounts/includes copying mezzanine/accounts/templates/accounts/includes/user_panel.html -> build/lib/mezzanine/accounts/templates/accounts/includes copying mezzanine/accounts/templates/accounts/includes/user_panel_nav.html -> build/lib/mezzanine/accounts/templates/accounts/includes creating build/lib/mezzanine/accounts/templates/admin copying mezzanine/accounts/templates/admin/profile_inline.html -> build/lib/mezzanine/accounts/templates/admin creating build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/account_approve.html -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/account_approve.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/account_approve_subject.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/account_approved.html -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/account_approved.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/account_approved_subject.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/password_reset_verify.html -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/password_reset_verify.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/password_reset_verify_subject.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/signup_verify.html -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/signup_verify.txt -> build/lib/mezzanine/accounts/templates/email copying mezzanine/accounts/templates/email/signup_verify_subject.txt -> build/lib/mezzanine/accounts/templates/email creating build/lib/mezzanine/accounts/templatetags copying mezzanine/accounts/templatetags/__init__.py -> build/lib/mezzanine/accounts/templatetags copying mezzanine/accounts/templatetags/accounts_tags.py -> build/lib/mezzanine/accounts/templatetags creating build/lib/mezzanine/bin copying mezzanine/bin/__init__.py -> build/lib/mezzanine/bin copying mezzanine/bin/mezzanine_project.py -> build/lib/mezzanine/bin creating build/lib/mezzanine/bin/management copying mezzanine/bin/management/__init__.py -> build/lib/mezzanine/bin/management creating build/lib/mezzanine/bin/management/commands copying mezzanine/bin/management/commands/__init__.py -> build/lib/mezzanine/bin/management/commands copying mezzanine/bin/management/commands/mezzanine_project.py -> build/lib/mezzanine/bin/management/commands creating build/lib/mezzanine/blog copying mezzanine/blog/__init__.py -> build/lib/mezzanine/blog copying mezzanine/blog/admin.py -> build/lib/mezzanine/blog copying mezzanine/blog/defaults.py -> build/lib/mezzanine/blog copying mezzanine/blog/feeds.py -> build/lib/mezzanine/blog copying mezzanine/blog/forms.py -> build/lib/mezzanine/blog copying mezzanine/blog/models.py -> build/lib/mezzanine/blog copying mezzanine/blog/translation.py -> build/lib/mezzanine/blog copying mezzanine/blog/urls.py -> build/lib/mezzanine/blog copying mezzanine/blog/views.py -> build/lib/mezzanine/blog creating build/lib/mezzanine/blog/locale/ar/LC_MESSAGES copying mezzanine/blog/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/ar/LC_MESSAGES copying mezzanine/blog/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/ar/LC_MESSAGES creating build/lib/mezzanine/blog/locale/bg/LC_MESSAGES copying mezzanine/blog/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/bg/LC_MESSAGES copying mezzanine/blog/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/bg/LC_MESSAGES creating build/lib/mezzanine/blog/locale/ca/LC_MESSAGES copying mezzanine/blog/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/ca/LC_MESSAGES copying mezzanine/blog/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/ca/LC_MESSAGES creating build/lib/mezzanine/blog/locale/cs/LC_MESSAGES copying mezzanine/blog/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/cs/LC_MESSAGES copying mezzanine/blog/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/cs/LC_MESSAGES creating build/lib/mezzanine/blog/locale/da/LC_MESSAGES copying mezzanine/blog/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/da/LC_MESSAGES copying mezzanine/blog/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/da/LC_MESSAGES creating build/lib/mezzanine/blog/locale/de/LC_MESSAGES copying mezzanine/blog/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/de/LC_MESSAGES copying mezzanine/blog/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/de/LC_MESSAGES creating build/lib/mezzanine/blog/locale/en/LC_MESSAGES copying mezzanine/blog/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/en/LC_MESSAGES copying mezzanine/blog/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/en/LC_MESSAGES creating build/lib/mezzanine/blog/locale/eo/LC_MESSAGES copying mezzanine/blog/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/eo/LC_MESSAGES copying mezzanine/blog/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/eo/LC_MESSAGES creating build/lib/mezzanine/blog/locale/es/LC_MESSAGES copying mezzanine/blog/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/es/LC_MESSAGES copying mezzanine/blog/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/es/LC_MESSAGES creating build/lib/mezzanine/blog/locale/et/LC_MESSAGES copying mezzanine/blog/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/et/LC_MESSAGES copying mezzanine/blog/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/et/LC_MESSAGES creating build/lib/mezzanine/blog/locale/fa/LC_MESSAGES copying mezzanine/blog/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/fa/LC_MESSAGES copying mezzanine/blog/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/fa/LC_MESSAGES creating build/lib/mezzanine/blog/locale/fa_IR/LC_MESSAGES copying mezzanine/blog/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/fa_IR/LC_MESSAGES copying mezzanine/blog/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/blog/locale/fi/LC_MESSAGES copying mezzanine/blog/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/fi/LC_MESSAGES copying mezzanine/blog/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/fi/LC_MESSAGES creating build/lib/mezzanine/blog/locale/fr/LC_MESSAGES copying mezzanine/blog/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/fr/LC_MESSAGES copying mezzanine/blog/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/fr/LC_MESSAGES creating build/lib/mezzanine/blog/locale/hr_HR/LC_MESSAGES copying mezzanine/blog/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/hr_HR/LC_MESSAGES copying mezzanine/blog/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/blog/locale/hu/LC_MESSAGES copying mezzanine/blog/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/hu/LC_MESSAGES copying mezzanine/blog/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/hu/LC_MESSAGES creating build/lib/mezzanine/blog/locale/id_ID/LC_MESSAGES copying mezzanine/blog/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/id_ID/LC_MESSAGES copying mezzanine/blog/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/blog/locale/is_IS/LC_MESSAGES copying mezzanine/blog/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/is_IS/LC_MESSAGES copying mezzanine/blog/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/blog/locale/it/LC_MESSAGES copying mezzanine/blog/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/it/LC_MESSAGES copying mezzanine/blog/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/it/LC_MESSAGES creating build/lib/mezzanine/blog/locale/ja/LC_MESSAGES copying mezzanine/blog/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/ja/LC_MESSAGES copying mezzanine/blog/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/ja/LC_MESSAGES creating build/lib/mezzanine/blog/locale/ko/LC_MESSAGES copying mezzanine/blog/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/ko/LC_MESSAGES copying mezzanine/blog/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/ko/LC_MESSAGES creating build/lib/mezzanine/blog/locale/lv/LC_MESSAGES copying mezzanine/blog/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/lv/LC_MESSAGES copying mezzanine/blog/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/lv/LC_MESSAGES creating build/lib/mezzanine/blog/locale/nb/LC_MESSAGES copying mezzanine/blog/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/nb/LC_MESSAGES copying mezzanine/blog/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/nb/LC_MESSAGES creating build/lib/mezzanine/blog/locale/nl/LC_MESSAGES copying mezzanine/blog/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/nl/LC_MESSAGES copying mezzanine/blog/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/nl/LC_MESSAGES creating build/lib/mezzanine/blog/locale/pap/LC_MESSAGES copying mezzanine/blog/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/pap/LC_MESSAGES copying mezzanine/blog/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/pap/LC_MESSAGES creating build/lib/mezzanine/blog/locale/pl/LC_MESSAGES copying mezzanine/blog/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/pl/LC_MESSAGES copying mezzanine/blog/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/pl/LC_MESSAGES creating build/lib/mezzanine/blog/locale/pt_BR/LC_MESSAGES copying mezzanine/blog/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/pt_BR/LC_MESSAGES copying mezzanine/blog/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/blog/locale/pt_PT/LC_MESSAGES copying mezzanine/blog/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/pt_PT/LC_MESSAGES copying mezzanine/blog/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/blog/locale/ru/LC_MESSAGES copying mezzanine/blog/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/ru/LC_MESSAGES copying mezzanine/blog/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/ru/LC_MESSAGES creating build/lib/mezzanine/blog/locale/sk/LC_MESSAGES copying mezzanine/blog/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/sk/LC_MESSAGES copying mezzanine/blog/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/sk/LC_MESSAGES creating build/lib/mezzanine/blog/locale/sr_Latn/LC_MESSAGES copying mezzanine/blog/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/sr_Latn/LC_MESSAGES copying mezzanine/blog/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/blog/locale/sv/LC_MESSAGES copying mezzanine/blog/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/sv/LC_MESSAGES copying mezzanine/blog/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/sv/LC_MESSAGES creating build/lib/mezzanine/blog/locale/tr/LC_MESSAGES copying mezzanine/blog/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/tr/LC_MESSAGES copying mezzanine/blog/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/tr/LC_MESSAGES creating build/lib/mezzanine/blog/locale/uk_UA/LC_MESSAGES copying mezzanine/blog/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/uk_UA/LC_MESSAGES copying mezzanine/blog/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/blog/locale/vi_VN/LC_MESSAGES copying mezzanine/blog/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/vi_VN/LC_MESSAGES copying mezzanine/blog/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/blog/locale/zh/LC_MESSAGES copying mezzanine/blog/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/zh/LC_MESSAGES copying mezzanine/blog/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/zh/LC_MESSAGES creating build/lib/mezzanine/blog/locale/zh_CN/LC_MESSAGES copying mezzanine/blog/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/zh_CN/LC_MESSAGES copying mezzanine/blog/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/blog/locale/zh_TW/LC_MESSAGES copying mezzanine/blog/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/blog/locale/zh_TW/LC_MESSAGES copying mezzanine/blog/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/blog/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/blog/management copying mezzanine/blog/management/__init__.py -> build/lib/mezzanine/blog/management copying mezzanine/blog/management/base.py -> build/lib/mezzanine/blog/management creating build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/__init__.py -> build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/import_blogger.py -> build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/import_blogml.py -> build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/import_posterous.py -> build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/import_rss.py -> build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/import_tumblr.py -> build/lib/mezzanine/blog/management/commands copying mezzanine/blog/management/commands/import_wordpress.py -> build/lib/mezzanine/blog/management/commands creating build/lib/mezzanine/blog/migrations copying mezzanine/blog/migrations/0001_initial.py -> build/lib/mezzanine/blog/migrations copying mezzanine/blog/migrations/0002_auto_20150527_1555.py -> build/lib/mezzanine/blog/migrations copying mezzanine/blog/migrations/0003_auto_20170411_0504.py -> build/lib/mezzanine/blog/migrations copying mezzanine/blog/migrations/__init__.py -> build/lib/mezzanine/blog/migrations creating build/lib/mezzanine/blog/templates/admin/includes copying mezzanine/blog/templates/admin/includes/quick_blog.html -> build/lib/mezzanine/blog/templates/admin/includes creating build/lib/mezzanine/blog/templates/blog copying mezzanine/blog/templates/blog/blog_post_detail.html -> build/lib/mezzanine/blog/templates/blog copying mezzanine/blog/templates/blog/blog_post_list.html -> build/lib/mezzanine/blog/templates/blog creating build/lib/mezzanine/blog/templates/blog/includes copying mezzanine/blog/templates/blog/includes/filter_panel.html -> build/lib/mezzanine/blog/templates/blog/includes creating build/lib/mezzanine/blog/templatetags copying mezzanine/blog/templatetags/__init__.py -> build/lib/mezzanine/blog/templatetags copying mezzanine/blog/templatetags/blog_tags.py -> build/lib/mezzanine/blog/templatetags creating build/lib/mezzanine/boot copying mezzanine/boot/__init__.py -> build/lib/mezzanine/boot copying mezzanine/boot/lazy_admin.py -> build/lib/mezzanine/boot copying mezzanine/boot/models.py -> build/lib/mezzanine/boot creating build/lib/mezzanine/conf copying mezzanine/conf/__init__.py -> build/lib/mezzanine/conf copying mezzanine/conf/admin.py -> build/lib/mezzanine/conf copying mezzanine/conf/context_processors.py -> build/lib/mezzanine/conf copying mezzanine/conf/forms.py -> build/lib/mezzanine/conf copying mezzanine/conf/models.py -> build/lib/mezzanine/conf copying mezzanine/conf/translation.py -> build/lib/mezzanine/conf creating build/lib/mezzanine/conf/locale/ar/LC_MESSAGES copying mezzanine/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/ar/LC_MESSAGES copying mezzanine/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/ar/LC_MESSAGES creating build/lib/mezzanine/conf/locale/bg/LC_MESSAGES copying mezzanine/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/bg/LC_MESSAGES copying mezzanine/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/bg/LC_MESSAGES creating build/lib/mezzanine/conf/locale/ca/LC_MESSAGES copying mezzanine/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/ca/LC_MESSAGES copying mezzanine/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/ca/LC_MESSAGES creating build/lib/mezzanine/conf/locale/cs/LC_MESSAGES copying mezzanine/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/cs/LC_MESSAGES copying mezzanine/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/cs/LC_MESSAGES creating build/lib/mezzanine/conf/locale/da/LC_MESSAGES copying mezzanine/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/da/LC_MESSAGES copying mezzanine/conf/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/da/LC_MESSAGES creating build/lib/mezzanine/conf/locale/de/LC_MESSAGES copying mezzanine/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/de/LC_MESSAGES copying mezzanine/conf/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/de/LC_MESSAGES creating build/lib/mezzanine/conf/locale/en/LC_MESSAGES copying mezzanine/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/en/LC_MESSAGES copying mezzanine/conf/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/en/LC_MESSAGES creating build/lib/mezzanine/conf/locale/eo/LC_MESSAGES copying mezzanine/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/eo/LC_MESSAGES copying mezzanine/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/eo/LC_MESSAGES creating build/lib/mezzanine/conf/locale/es/LC_MESSAGES copying mezzanine/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/es/LC_MESSAGES copying mezzanine/conf/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/es/LC_MESSAGES creating build/lib/mezzanine/conf/locale/et/LC_MESSAGES copying mezzanine/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/et/LC_MESSAGES copying mezzanine/conf/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/et/LC_MESSAGES creating build/lib/mezzanine/conf/locale/fa/LC_MESSAGES copying mezzanine/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/fa/LC_MESSAGES copying mezzanine/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/fa/LC_MESSAGES creating build/lib/mezzanine/conf/locale/fa_IR/LC_MESSAGES copying mezzanine/conf/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/fa_IR/LC_MESSAGES copying mezzanine/conf/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/conf/locale/fi/LC_MESSAGES copying mezzanine/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/fi/LC_MESSAGES copying mezzanine/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/fi/LC_MESSAGES creating build/lib/mezzanine/conf/locale/fr/LC_MESSAGES copying mezzanine/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/fr/LC_MESSAGES copying mezzanine/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/fr/LC_MESSAGES creating build/lib/mezzanine/conf/locale/hr_HR/LC_MESSAGES copying mezzanine/conf/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/hr_HR/LC_MESSAGES copying mezzanine/conf/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/conf/locale/hu/LC_MESSAGES copying mezzanine/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/hu/LC_MESSAGES copying mezzanine/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/hu/LC_MESSAGES creating build/lib/mezzanine/conf/locale/id_ID/LC_MESSAGES copying mezzanine/conf/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/id_ID/LC_MESSAGES copying mezzanine/conf/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/conf/locale/is_IS/LC_MESSAGES copying mezzanine/conf/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/is_IS/LC_MESSAGES copying mezzanine/conf/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/conf/locale/it/LC_MESSAGES copying mezzanine/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/it/LC_MESSAGES copying mezzanine/conf/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/it/LC_MESSAGES creating build/lib/mezzanine/conf/locale/ja/LC_MESSAGES copying mezzanine/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/ja/LC_MESSAGES copying mezzanine/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/ja/LC_MESSAGES creating build/lib/mezzanine/conf/locale/ko/LC_MESSAGES copying mezzanine/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/ko/LC_MESSAGES copying mezzanine/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/ko/LC_MESSAGES creating build/lib/mezzanine/conf/locale/lv/LC_MESSAGES copying mezzanine/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/lv/LC_MESSAGES copying mezzanine/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/lv/LC_MESSAGES creating build/lib/mezzanine/conf/locale/nb/LC_MESSAGES copying mezzanine/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/nb/LC_MESSAGES copying mezzanine/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/nb/LC_MESSAGES creating build/lib/mezzanine/conf/locale/nl/LC_MESSAGES copying mezzanine/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/nl/LC_MESSAGES copying mezzanine/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/nl/LC_MESSAGES creating build/lib/mezzanine/conf/locale/pap/LC_MESSAGES copying mezzanine/conf/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/pap/LC_MESSAGES copying mezzanine/conf/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/pap/LC_MESSAGES creating build/lib/mezzanine/conf/locale/pl/LC_MESSAGES copying mezzanine/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/pl/LC_MESSAGES copying mezzanine/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/pl/LC_MESSAGES creating build/lib/mezzanine/conf/locale/pt_BR/LC_MESSAGES copying mezzanine/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/pt_BR/LC_MESSAGES copying mezzanine/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/conf/locale/pt_PT/LC_MESSAGES copying mezzanine/conf/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/pt_PT/LC_MESSAGES copying mezzanine/conf/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/conf/locale/ru/LC_MESSAGES copying mezzanine/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/ru/LC_MESSAGES copying mezzanine/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/ru/LC_MESSAGES creating build/lib/mezzanine/conf/locale/sk/LC_MESSAGES copying mezzanine/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/sk/LC_MESSAGES copying mezzanine/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/sk/LC_MESSAGES creating build/lib/mezzanine/conf/locale/sr_Latn/LC_MESSAGES copying mezzanine/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/sr_Latn/LC_MESSAGES copying mezzanine/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/conf/locale/sv/LC_MESSAGES copying mezzanine/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/sv/LC_MESSAGES copying mezzanine/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/sv/LC_MESSAGES creating build/lib/mezzanine/conf/locale/tr/LC_MESSAGES copying mezzanine/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/tr/LC_MESSAGES copying mezzanine/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/tr/LC_MESSAGES creating build/lib/mezzanine/conf/locale/uk_UA/LC_MESSAGES copying mezzanine/conf/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/uk_UA/LC_MESSAGES copying mezzanine/conf/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/conf/locale/vi_VN/LC_MESSAGES copying mezzanine/conf/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/vi_VN/LC_MESSAGES copying mezzanine/conf/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/conf/locale/zh/LC_MESSAGES copying mezzanine/conf/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/zh/LC_MESSAGES copying mezzanine/conf/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/zh/LC_MESSAGES creating build/lib/mezzanine/conf/locale/zh_CN/LC_MESSAGES copying mezzanine/conf/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/zh_CN/LC_MESSAGES copying mezzanine/conf/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/conf/locale/zh_TW/LC_MESSAGES copying mezzanine/conf/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/conf/locale/zh_TW/LC_MESSAGES copying mezzanine/conf/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/conf/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/conf/migrations copying mezzanine/conf/migrations/0001_initial.py -> build/lib/mezzanine/conf/migrations copying mezzanine/conf/migrations/__init__.py -> build/lib/mezzanine/conf/migrations creating build/lib/mezzanine/conf/static/mezzanine/css/admin copying mezzanine/conf/static/mezzanine/css/admin/settings.css -> build/lib/mezzanine/conf/static/mezzanine/css/admin creating build/lib/mezzanine/conf/static/mezzanine/js/admin copying mezzanine/conf/static/mezzanine/js/admin/tabbed_translatable_settings.js -> build/lib/mezzanine/conf/static/mezzanine/js/admin creating build/lib/mezzanine/conf/templates/admin/conf/setting copying mezzanine/conf/templates/admin/conf/setting/change_list.html -> build/lib/mezzanine/conf/templates/admin/conf/setting creating build/lib/mezzanine/core copying mezzanine/core/__init__.py -> build/lib/mezzanine/core copying mezzanine/core/admin.py -> build/lib/mezzanine/core copying mezzanine/core/apps.py -> build/lib/mezzanine/core copying mezzanine/core/auth_backends.py -> build/lib/mezzanine/core copying mezzanine/core/checks.py -> build/lib/mezzanine/core copying mezzanine/core/defaults.py -> build/lib/mezzanine/core copying mezzanine/core/exceptions.py -> build/lib/mezzanine/core copying mezzanine/core/fields.py -> build/lib/mezzanine/core copying mezzanine/core/forms.py -> build/lib/mezzanine/core copying mezzanine/core/managers.py -> build/lib/mezzanine/core copying mezzanine/core/middleware.py -> build/lib/mezzanine/core copying mezzanine/core/models.py -> build/lib/mezzanine/core copying mezzanine/core/request.py -> build/lib/mezzanine/core copying mezzanine/core/sitemaps.py -> build/lib/mezzanine/core copying mezzanine/core/translation.py -> build/lib/mezzanine/core copying mezzanine/core/urls.py -> build/lib/mezzanine/core copying mezzanine/core/views.py -> build/lib/mezzanine/core creating build/lib/mezzanine/core/locale/ar/LC_MESSAGES copying mezzanine/core/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/ar/LC_MESSAGES copying mezzanine/core/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/ar/LC_MESSAGES creating build/lib/mezzanine/core/locale/bg/LC_MESSAGES copying mezzanine/core/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/bg/LC_MESSAGES copying mezzanine/core/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/bg/LC_MESSAGES creating build/lib/mezzanine/core/locale/ca/LC_MESSAGES copying mezzanine/core/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/ca/LC_MESSAGES copying mezzanine/core/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/ca/LC_MESSAGES creating build/lib/mezzanine/core/locale/cs/LC_MESSAGES copying mezzanine/core/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/cs/LC_MESSAGES copying mezzanine/core/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/cs/LC_MESSAGES creating build/lib/mezzanine/core/locale/da/LC_MESSAGES copying mezzanine/core/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/da/LC_MESSAGES copying mezzanine/core/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/da/LC_MESSAGES creating build/lib/mezzanine/core/locale/de/LC_MESSAGES copying mezzanine/core/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/de/LC_MESSAGES copying mezzanine/core/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/de/LC_MESSAGES creating build/lib/mezzanine/core/locale/en/LC_MESSAGES copying mezzanine/core/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/en/LC_MESSAGES copying mezzanine/core/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/en/LC_MESSAGES creating build/lib/mezzanine/core/locale/eo/LC_MESSAGES copying mezzanine/core/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/eo/LC_MESSAGES copying mezzanine/core/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/eo/LC_MESSAGES creating build/lib/mezzanine/core/locale/es/LC_MESSAGES copying mezzanine/core/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/es/LC_MESSAGES copying mezzanine/core/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/es/LC_MESSAGES creating build/lib/mezzanine/core/locale/et/LC_MESSAGES copying mezzanine/core/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/et/LC_MESSAGES copying mezzanine/core/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/et/LC_MESSAGES creating build/lib/mezzanine/core/locale/fa/LC_MESSAGES copying mezzanine/core/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/fa/LC_MESSAGES copying mezzanine/core/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/fa/LC_MESSAGES creating build/lib/mezzanine/core/locale/fa_IR/LC_MESSAGES copying mezzanine/core/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/fa_IR/LC_MESSAGES copying mezzanine/core/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/core/locale/fi/LC_MESSAGES copying mezzanine/core/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/fi/LC_MESSAGES copying mezzanine/core/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/fi/LC_MESSAGES creating build/lib/mezzanine/core/locale/fr/LC_MESSAGES copying mezzanine/core/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/fr/LC_MESSAGES copying mezzanine/core/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/fr/LC_MESSAGES creating build/lib/mezzanine/core/locale/hr_HR/LC_MESSAGES copying mezzanine/core/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/hr_HR/LC_MESSAGES copying mezzanine/core/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/core/locale/hu/LC_MESSAGES copying mezzanine/core/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/hu/LC_MESSAGES copying mezzanine/core/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/hu/LC_MESSAGES creating build/lib/mezzanine/core/locale/id_ID/LC_MESSAGES copying mezzanine/core/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/id_ID/LC_MESSAGES copying mezzanine/core/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/core/locale/is_IS/LC_MESSAGES copying mezzanine/core/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/is_IS/LC_MESSAGES copying mezzanine/core/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/core/locale/it/LC_MESSAGES copying mezzanine/core/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/it/LC_MESSAGES copying mezzanine/core/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/it/LC_MESSAGES creating build/lib/mezzanine/core/locale/ja/LC_MESSAGES copying mezzanine/core/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/ja/LC_MESSAGES copying mezzanine/core/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/ja/LC_MESSAGES creating build/lib/mezzanine/core/locale/ko/LC_MESSAGES copying mezzanine/core/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/ko/LC_MESSAGES copying mezzanine/core/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/ko/LC_MESSAGES creating build/lib/mezzanine/core/locale/lv/LC_MESSAGES copying mezzanine/core/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/lv/LC_MESSAGES copying mezzanine/core/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/lv/LC_MESSAGES creating build/lib/mezzanine/core/locale/nb/LC_MESSAGES copying mezzanine/core/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/nb/LC_MESSAGES copying mezzanine/core/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/nb/LC_MESSAGES creating build/lib/mezzanine/core/locale/nl/LC_MESSAGES copying mezzanine/core/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/nl/LC_MESSAGES copying mezzanine/core/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/nl/LC_MESSAGES creating build/lib/mezzanine/core/locale/pap/LC_MESSAGES copying mezzanine/core/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/pap/LC_MESSAGES copying mezzanine/core/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/pap/LC_MESSAGES creating build/lib/mezzanine/core/locale/pl/LC_MESSAGES copying mezzanine/core/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/pl/LC_MESSAGES copying mezzanine/core/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/pl/LC_MESSAGES creating build/lib/mezzanine/core/locale/pt_BR/LC_MESSAGES copying mezzanine/core/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/pt_BR/LC_MESSAGES copying mezzanine/core/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/core/locale/pt_PT/LC_MESSAGES copying mezzanine/core/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/pt_PT/LC_MESSAGES copying mezzanine/core/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/core/locale/ru/LC_MESSAGES copying mezzanine/core/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/ru/LC_MESSAGES copying mezzanine/core/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/ru/LC_MESSAGES creating build/lib/mezzanine/core/locale/sk/LC_MESSAGES copying mezzanine/core/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/sk/LC_MESSAGES copying mezzanine/core/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/sk/LC_MESSAGES creating build/lib/mezzanine/core/locale/sr_Latn/LC_MESSAGES copying mezzanine/core/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/sr_Latn/LC_MESSAGES copying mezzanine/core/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/core/locale/sv/LC_MESSAGES copying mezzanine/core/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/sv/LC_MESSAGES copying mezzanine/core/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/sv/LC_MESSAGES creating build/lib/mezzanine/core/locale/tr/LC_MESSAGES copying mezzanine/core/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/tr/LC_MESSAGES copying mezzanine/core/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/tr/LC_MESSAGES creating build/lib/mezzanine/core/locale/uk_UA/LC_MESSAGES copying mezzanine/core/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/uk_UA/LC_MESSAGES copying mezzanine/core/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/core/locale/vi_VN/LC_MESSAGES copying mezzanine/core/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/vi_VN/LC_MESSAGES copying mezzanine/core/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/core/locale/zh/LC_MESSAGES copying mezzanine/core/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/zh/LC_MESSAGES copying mezzanine/core/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/zh/LC_MESSAGES creating build/lib/mezzanine/core/locale/zh_CN/LC_MESSAGES copying mezzanine/core/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/zh_CN/LC_MESSAGES copying mezzanine/core/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/core/locale/zh_TW/LC_MESSAGES copying mezzanine/core/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/core/locale/zh_TW/LC_MESSAGES copying mezzanine/core/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/core/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/core/management copying mezzanine/core/management/__init__.py -> build/lib/mezzanine/core/management creating build/lib/mezzanine/core/management/commands copying mezzanine/core/management/commands/__init__.py -> build/lib/mezzanine/core/management/commands copying mezzanine/core/management/commands/collecttemplates.py -> build/lib/mezzanine/core/management/commands copying mezzanine/core/management/commands/createdb.py -> build/lib/mezzanine/core/management/commands copying mezzanine/core/management/commands/runserver.py -> build/lib/mezzanine/core/management/commands creating build/lib/mezzanine/core/migrations copying mezzanine/core/migrations/0001_initial.py -> build/lib/mezzanine/core/migrations copying mezzanine/core/migrations/0002_auto_20150414_2140.py -> build/lib/mezzanine/core/migrations copying mezzanine/core/migrations/__init__.py -> build/lib/mezzanine/core/migrations creating build/lib/mezzanine/core/static copying mezzanine/core/static/robots.txt -> build/lib/mezzanine/core/static creating build/lib/mezzanine/core/static/admin/img/admin copying mezzanine/core/static/admin/img/admin/README -> build/lib/mezzanine/core/static/admin/img/admin copying mezzanine/core/static/admin/img/admin/arrow-down.gif -> build/lib/mezzanine/core/static/admin/img/admin copying mezzanine/core/static/admin/img/admin/arrow-up.gif -> build/lib/mezzanine/core/static/admin/img/admin copying mezzanine/core/static/admin/img/admin/icon_deletelink.gif -> build/lib/mezzanine/core/static/admin/img/admin creating build/lib/mezzanine/core/static/admin/js copying mezzanine/core/static/admin/js/collapse.js -> build/lib/mezzanine/core/static/admin/js creating build/lib/mezzanine/core/static/css copying mezzanine/core/static/css/bootstrap-rtl.css -> build/lib/mezzanine/core/static/css copying mezzanine/core/static/css/bootstrap-theme.css -> build/lib/mezzanine/core/static/css copying mezzanine/core/static/css/bootstrap.css -> build/lib/mezzanine/core/static/css copying mezzanine/core/static/css/mezzanine.css -> build/lib/mezzanine/core/static/css creating build/lib/mezzanine/core/static/fonts copying mezzanine/core/static/fonts/glyphicons-halflings-regular.eot -> build/lib/mezzanine/core/static/fonts copying mezzanine/core/static/fonts/glyphicons-halflings-regular.svg -> build/lib/mezzanine/core/static/fonts copying mezzanine/core/static/fonts/glyphicons-halflings-regular.ttf -> build/lib/mezzanine/core/static/fonts copying mezzanine/core/static/fonts/glyphicons-halflings-regular.woff -> build/lib/mezzanine/core/static/fonts creating build/lib/mezzanine/core/static/img copying mezzanine/core/static/img/favicon.ico -> build/lib/mezzanine/core/static/img creating build/lib/mezzanine/core/static/js copying mezzanine/core/static/js/bootstrap-extras.js -> build/lib/mezzanine/core/static/js copying mezzanine/core/static/js/bootstrap.js -> build/lib/mezzanine/core/static/js copying mezzanine/core/static/js/html5shiv.js -> build/lib/mezzanine/core/static/js copying mezzanine/core/static/js/respond.min.js -> build/lib/mezzanine/core/static/js creating build/lib/mezzanine/core/static/mezzanine/chosen copying mezzanine/core/static/mezzanine/chosen/chosen-0.9.12.jquery.js -> build/lib/mezzanine/core/static/mezzanine/chosen copying mezzanine/core/static/mezzanine/chosen/chosen-sprite-dark.png -> build/lib/mezzanine/core/static/mezzanine/chosen copying mezzanine/core/static/mezzanine/chosen/chosen-sprite.png -> build/lib/mezzanine/core/static/mezzanine/chosen copying mezzanine/core/static/mezzanine/chosen/chosen.css -> build/lib/mezzanine/core/static/mezzanine/chosen creating build/lib/mezzanine/core/static/mezzanine/css copying mezzanine/core/static/mezzanine/css/editable.css -> build/lib/mezzanine/core/static/mezzanine/css copying mezzanine/core/static/mezzanine/css/tinymce.css -> build/lib/mezzanine/core/static/mezzanine/css creating build/lib/mezzanine/core/static/mezzanine/css/admin copying mezzanine/core/static/mezzanine/css/admin/dashboard.css -> build/lib/mezzanine/core/static/mezzanine/css/admin copying mezzanine/core/static/mezzanine/css/admin/global.css -> build/lib/mezzanine/core/static/mezzanine/css/admin copying mezzanine/core/static/mezzanine/css/admin/rtl.css -> build/lib/mezzanine/core/static/mezzanine/css/admin copying mezzanine/core/static/mezzanine/css/admin/tabbed_translation_fields.css -> build/lib/mezzanine/core/static/mezzanine/css/admin creating build/lib/mezzanine/core/static/mezzanine/css/smoothness copying mezzanine/core/static/mezzanine/css/smoothness/jquery-ui.css -> build/lib/mezzanine/core/static/mezzanine/css/smoothness copying mezzanine/core/static/mezzanine/css/smoothness/jquery-ui.min.css -> build/lib/mezzanine/core/static/mezzanine/css/smoothness creating build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_flat_75_ffffff_40x100.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_75_dadada_1x400.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_222222_256x240.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_2e83ff_256x240.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_454545_256x240.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_888888_256x240.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images copying mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_cd0a0a_256x240.png -> build/lib/mezzanine/core/static/mezzanine/css/smoothness/images creating build/lib/mezzanine/core/static/mezzanine/img copying mezzanine/core/static/mezzanine/img/loadingAnimation.gif -> build/lib/mezzanine/core/static/mezzanine/img creating build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/editable.js -> build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/jquery-3.4.1.js -> build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/jquery-ui-1.12.1.js -> build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/jquery.form.js -> build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/jquery.tools.overlay.js -> build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/jquery.tools.toolbox.expose.js -> build/lib/mezzanine/core/static/mezzanine/js copying mezzanine/core/static/mezzanine/js/tinymce_setup.js -> build/lib/mezzanine/core/static/mezzanine/js creating build/lib/mezzanine/core/static/mezzanine/js/admin copying mezzanine/core/static/mezzanine/js/admin/ajax_csrf.js -> build/lib/mezzanine/core/static/mezzanine/js/admin copying mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js -> build/lib/mezzanine/core/static/mezzanine/js/admin copying mezzanine/core/static/mezzanine/js/admin/keywords_field.js -> build/lib/mezzanine/core/static/mezzanine/js/admin copying mezzanine/core/static/mezzanine/js/admin/login.js -> build/lib/mezzanine/core/static/mezzanine/js/admin copying mezzanine/core/static/mezzanine/js/admin/navigation.js -> build/lib/mezzanine/core/static/mezzanine/js/admin copying mezzanine/core/static/mezzanine/js/admin/tabbed_translation_fields.js -> build/lib/mezzanine/core/static/mezzanine/js/admin creating build/lib/mezzanine/core/static/mezzanine/tinymce copying mezzanine/core/static/mezzanine/tinymce/jquery.tinymce.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce copying mezzanine/core/static/mezzanine/tinymce/license.txt -> build/lib/mezzanine/core/static/mezzanine/tinymce copying mezzanine/core/static/mezzanine/tinymce/tinymce.css -> build/lib/mezzanine/core/static/mezzanine/tinymce copying mezzanine/core/static/mezzanine/tinymce/tinymce.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce creating build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/ar.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/ca.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/cs.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/da.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/de.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/es.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/et.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/fa.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/fa_IR.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/fi.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/fr_FR.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/hr.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/hu_HU.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/id.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/is_IS.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/it.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/ja.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/ko_KR.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/lv.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/nb_NO.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/nl.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/pl.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/pt_BR.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/pt_PT.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/ru.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/sk.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/sr.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/sv_SE.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/tr.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/uk_UA.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/vi.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/zh_CN.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs copying mezzanine/core/static/mezzanine/tinymce/langs/zh_TW.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/langs creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/advlist copying mezzanine/core/static/mezzanine/tinymce/plugins/advlist/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/advlist creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/anchor copying mezzanine/core/static/mezzanine/tinymce/plugins/anchor/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/anchor creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autolink copying mezzanine/core/static/mezzanine/tinymce/plugins/autolink/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autolink creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autoresize copying mezzanine/core/static/mezzanine/tinymce/plugins/autoresize/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autoresize creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autosave copying mezzanine/core/static/mezzanine/tinymce/plugins/autosave/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autosave creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/bbcode copying mezzanine/core/static/mezzanine/tinymce/plugins/bbcode/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/bbcode creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/charmap copying mezzanine/core/static/mezzanine/tinymce/plugins/charmap/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/charmap creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/code copying mezzanine/core/static/mezzanine/tinymce/plugins/code/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/code creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker copying mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu copying mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/directionality copying mezzanine/core/static/mezzanine/tinymce/plugins/directionality/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/directionality creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-cool.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-cry.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-embarassed.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-foot-in-mouth.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-frown.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-innocent.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-kiss.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-laughing.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-money-mouth.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-sealed.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-smile.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-surprised.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-tongue-out.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-undecided.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-wink.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-yell.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example copying mezzanine/core/static/mezzanine/tinymce/plugins/example/dialog.html -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example copying mezzanine/core/static/mezzanine/tinymce/plugins/example/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency copying mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/fullpage copying mezzanine/core/static/mezzanine/tinymce/plugins/fullpage/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/fullpage creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen copying mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/hr copying mezzanine/core/static/mezzanine/tinymce/plugins/hr/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/hr creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/image copying mezzanine/core/static/mezzanine/tinymce/plugins/image/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/image creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/imagetools copying mezzanine/core/static/mezzanine/tinymce/plugins/imagetools/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/imagetools creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/importcss copying mezzanine/core/static/mezzanine/tinymce/plugins/importcss/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/importcss creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime copying mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/layer copying mezzanine/core/static/mezzanine/tinymce/plugins/layer/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/layer creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput copying mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/link copying mezzanine/core/static/mezzanine/tinymce/plugins/link/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/link creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/lists copying mezzanine/core/static/mezzanine/tinymce/plugins/lists/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/lists creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/media copying mezzanine/core/static/mezzanine/tinymce/plugins/media/moxieplayer.swf -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/media copying mezzanine/core/static/mezzanine/tinymce/plugins/media/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/media creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking copying mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/noneditable copying mezzanine/core/static/mezzanine/tinymce/plugins/noneditable/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/noneditable creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak copying mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/paste copying mezzanine/core/static/mezzanine/tinymce/plugins/paste/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/paste creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/preview copying mezzanine/core/static/mezzanine/tinymce/plugins/preview/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/preview creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/print copying mezzanine/core/static/mezzanine/tinymce/plugins/print/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/print creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/save copying mezzanine/core/static/mezzanine/tinymce/plugins/save/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/save creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace copying mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker copying mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus copying mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/table copying mezzanine/core/static/mezzanine/tinymce/plugins/table/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/table creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/template copying mezzanine/core/static/mezzanine/tinymce/plugins/template/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/template creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/textcolor copying mezzanine/core/static/mezzanine/tinymce/plugins/textcolor/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/textcolor creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/textpattern copying mezzanine/core/static/mezzanine/tinymce/plugins/textpattern/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/textpattern creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks copying mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css copying mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css/visualblocks.css -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualchars copying mezzanine/core/static/mezzanine/tinymce/plugins/visualchars/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualchars creating build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/wordcount copying mezzanine/core/static/mezzanine/tinymce/plugins/wordcount/plugin.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/wordcount creating build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/content.inline.min.css -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/content.min.css -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/skin.ie7.min.css -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/skin.min.css -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray creating build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.eot -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.svg -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.ttf -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.woff -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.eot -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.svg -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.ttf -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.woff -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts creating build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/anchor.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/loader.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/object.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/trans.gif -> build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img creating build/lib/mezzanine/core/static/mezzanine/tinymce/themes/modern copying mezzanine/core/static/mezzanine/tinymce/themes/modern/theme.min.js -> build/lib/mezzanine/core/static/mezzanine/tinymce/themes/modern creating build/lib/mezzanine/core/static/test copying mezzanine/core/static/test/gallery.zip -> build/lib/mezzanine/core/static/test copying mezzanine/core/static/test/image.jpg -> build/lib/mezzanine/core/static/test creating build/lib/mezzanine/core/templates copying mezzanine/core/templates/base.html -> build/lib/mezzanine/core/templates copying mezzanine/core/templates/index.html -> build/lib/mezzanine/core/templates copying mezzanine/core/templates/search_results.html -> build/lib/mezzanine/core/templates creating build/lib/mezzanine/core/templates/admin copying mezzanine/core/templates/admin/base_site.html -> build/lib/mezzanine/core/templates/admin copying mezzanine/core/templates/admin/index.html -> build/lib/mezzanine/core/templates/admin copying mezzanine/core/templates/admin/login.html -> build/lib/mezzanine/core/templates/admin creating build/lib/mezzanine/core/templates/admin/includes copying mezzanine/core/templates/admin/includes/app_list.html -> build/lib/mezzanine/core/templates/admin/includes copying mezzanine/core/templates/admin/includes/content_typed_change_list.html -> build/lib/mezzanine/core/templates/admin/includes copying mezzanine/core/templates/admin/includes/dropdown_menu.html -> build/lib/mezzanine/core/templates/admin/includes copying mezzanine/core/templates/admin/includes/recent_actions.html -> build/lib/mezzanine/core/templates/admin/includes creating build/lib/mezzanine/core/templates/email copying mezzanine/core/templates/email/base.html -> build/lib/mezzanine/core/templates/email copying mezzanine/core/templates/email/base.txt -> build/lib/mezzanine/core/templates/email creating build/lib/mezzanine/core/templates/errors copying mezzanine/core/templates/errors/404.html -> build/lib/mezzanine/core/templates/errors copying mezzanine/core/templates/errors/500.html -> build/lib/mezzanine/core/templates/errors creating build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/editable_form.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/editable_loader.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/editable_toolbar.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/footer_scripts.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/form_errors.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/form_fields.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/language_selector.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/pagination.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/search_form.html -> build/lib/mezzanine/core/templates/includes copying mezzanine/core/templates/includes/user_panel.html -> build/lib/mezzanine/core/templates/includes creating build/lib/mezzanine/core/templatetags copying mezzanine/core/templatetags/__init__.py -> build/lib/mezzanine/core/templatetags copying mezzanine/core/templatetags/mezzanine_tags.py -> build/lib/mezzanine/core/templatetags creating build/lib/mezzanine/forms copying mezzanine/forms/__init__.py -> build/lib/mezzanine/forms copying mezzanine/forms/admin.py -> build/lib/mezzanine/forms copying mezzanine/forms/defaults.py -> build/lib/mezzanine/forms copying mezzanine/forms/fields.py -> build/lib/mezzanine/forms copying mezzanine/forms/forms.py -> build/lib/mezzanine/forms copying mezzanine/forms/models.py -> build/lib/mezzanine/forms copying mezzanine/forms/page_processors.py -> build/lib/mezzanine/forms copying mezzanine/forms/signals.py -> build/lib/mezzanine/forms copying mezzanine/forms/translation.py -> build/lib/mezzanine/forms creating build/lib/mezzanine/forms/fixtures copying mezzanine/forms/fixtures/mezzanine_optional.json -> build/lib/mezzanine/forms/fixtures creating build/lib/mezzanine/forms/locale/ar/LC_MESSAGES copying mezzanine/forms/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/ar/LC_MESSAGES copying mezzanine/forms/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/ar/LC_MESSAGES creating build/lib/mezzanine/forms/locale/bg/LC_MESSAGES copying mezzanine/forms/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/bg/LC_MESSAGES copying mezzanine/forms/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/bg/LC_MESSAGES creating build/lib/mezzanine/forms/locale/ca/LC_MESSAGES copying mezzanine/forms/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/ca/LC_MESSAGES copying mezzanine/forms/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/ca/LC_MESSAGES creating build/lib/mezzanine/forms/locale/cs/LC_MESSAGES copying mezzanine/forms/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/cs/LC_MESSAGES copying mezzanine/forms/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/cs/LC_MESSAGES creating build/lib/mezzanine/forms/locale/da/LC_MESSAGES copying mezzanine/forms/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/da/LC_MESSAGES copying mezzanine/forms/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/da/LC_MESSAGES creating build/lib/mezzanine/forms/locale/de/LC_MESSAGES copying mezzanine/forms/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/de/LC_MESSAGES copying mezzanine/forms/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/de/LC_MESSAGES creating build/lib/mezzanine/forms/locale/en/LC_MESSAGES copying mezzanine/forms/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/en/LC_MESSAGES copying mezzanine/forms/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/en/LC_MESSAGES creating build/lib/mezzanine/forms/locale/eo/LC_MESSAGES copying mezzanine/forms/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/eo/LC_MESSAGES copying mezzanine/forms/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/eo/LC_MESSAGES creating build/lib/mezzanine/forms/locale/es/LC_MESSAGES copying mezzanine/forms/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/es/LC_MESSAGES copying mezzanine/forms/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/es/LC_MESSAGES creating build/lib/mezzanine/forms/locale/et/LC_MESSAGES copying mezzanine/forms/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/et/LC_MESSAGES copying mezzanine/forms/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/et/LC_MESSAGES creating build/lib/mezzanine/forms/locale/fa/LC_MESSAGES copying mezzanine/forms/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/fa/LC_MESSAGES copying mezzanine/forms/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/fa/LC_MESSAGES creating build/lib/mezzanine/forms/locale/fa_IR/LC_MESSAGES copying mezzanine/forms/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/fa_IR/LC_MESSAGES copying mezzanine/forms/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/forms/locale/fi/LC_MESSAGES copying mezzanine/forms/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/fi/LC_MESSAGES copying mezzanine/forms/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/fi/LC_MESSAGES creating build/lib/mezzanine/forms/locale/fr/LC_MESSAGES copying mezzanine/forms/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/fr/LC_MESSAGES copying mezzanine/forms/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/fr/LC_MESSAGES creating build/lib/mezzanine/forms/locale/hr_HR/LC_MESSAGES copying mezzanine/forms/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/hr_HR/LC_MESSAGES copying mezzanine/forms/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/forms/locale/hu/LC_MESSAGES copying mezzanine/forms/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/hu/LC_MESSAGES copying mezzanine/forms/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/hu/LC_MESSAGES creating build/lib/mezzanine/forms/locale/id_ID/LC_MESSAGES copying mezzanine/forms/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/id_ID/LC_MESSAGES copying mezzanine/forms/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/forms/locale/is_IS/LC_MESSAGES copying mezzanine/forms/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/is_IS/LC_MESSAGES copying mezzanine/forms/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/forms/locale/it/LC_MESSAGES copying mezzanine/forms/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/it/LC_MESSAGES copying mezzanine/forms/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/it/LC_MESSAGES creating build/lib/mezzanine/forms/locale/ja/LC_MESSAGES copying mezzanine/forms/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/ja/LC_MESSAGES copying mezzanine/forms/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/ja/LC_MESSAGES creating build/lib/mezzanine/forms/locale/ko/LC_MESSAGES copying mezzanine/forms/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/ko/LC_MESSAGES copying mezzanine/forms/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/ko/LC_MESSAGES creating build/lib/mezzanine/forms/locale/lv/LC_MESSAGES copying mezzanine/forms/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/lv/LC_MESSAGES copying mezzanine/forms/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/lv/LC_MESSAGES creating build/lib/mezzanine/forms/locale/nb/LC_MESSAGES copying mezzanine/forms/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/nb/LC_MESSAGES copying mezzanine/forms/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/nb/LC_MESSAGES creating build/lib/mezzanine/forms/locale/nl/LC_MESSAGES copying mezzanine/forms/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/nl/LC_MESSAGES copying mezzanine/forms/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/nl/LC_MESSAGES creating build/lib/mezzanine/forms/locale/pap/LC_MESSAGES copying mezzanine/forms/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/pap/LC_MESSAGES copying mezzanine/forms/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/pap/LC_MESSAGES creating build/lib/mezzanine/forms/locale/pl/LC_MESSAGES copying mezzanine/forms/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/pl/LC_MESSAGES copying mezzanine/forms/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/pl/LC_MESSAGES creating build/lib/mezzanine/forms/locale/pt_BR/LC_MESSAGES copying mezzanine/forms/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/pt_BR/LC_MESSAGES copying mezzanine/forms/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/forms/locale/pt_PT/LC_MESSAGES copying mezzanine/forms/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/pt_PT/LC_MESSAGES copying mezzanine/forms/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/forms/locale/ru/LC_MESSAGES copying mezzanine/forms/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/ru/LC_MESSAGES copying mezzanine/forms/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/ru/LC_MESSAGES creating build/lib/mezzanine/forms/locale/sk/LC_MESSAGES copying mezzanine/forms/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/sk/LC_MESSAGES copying mezzanine/forms/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/sk/LC_MESSAGES creating build/lib/mezzanine/forms/locale/sr_Latn/LC_MESSAGES copying mezzanine/forms/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/sr_Latn/LC_MESSAGES copying mezzanine/forms/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/forms/locale/sv/LC_MESSAGES copying mezzanine/forms/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/sv/LC_MESSAGES copying mezzanine/forms/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/sv/LC_MESSAGES creating build/lib/mezzanine/forms/locale/tr/LC_MESSAGES copying mezzanine/forms/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/tr/LC_MESSAGES copying mezzanine/forms/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/tr/LC_MESSAGES creating build/lib/mezzanine/forms/locale/uk_UA/LC_MESSAGES copying mezzanine/forms/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/uk_UA/LC_MESSAGES copying mezzanine/forms/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/forms/locale/vi_VN/LC_MESSAGES copying mezzanine/forms/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/vi_VN/LC_MESSAGES copying mezzanine/forms/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/forms/locale/zh/LC_MESSAGES copying mezzanine/forms/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/zh/LC_MESSAGES copying mezzanine/forms/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/zh/LC_MESSAGES creating build/lib/mezzanine/forms/locale/zh_CN/LC_MESSAGES copying mezzanine/forms/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/zh_CN/LC_MESSAGES copying mezzanine/forms/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/forms/locale/zh_TW/LC_MESSAGES copying mezzanine/forms/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/forms/locale/zh_TW/LC_MESSAGES copying mezzanine/forms/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/forms/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/0001_initial.py -> build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/0002_auto_20141227_0224.py -> build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/0003_emailfield.py -> build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/0004_auto_20150517_0510.py -> build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/0005_auto_20151026_1600.py -> build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/0006_auto_20170425_2225.py -> build/lib/mezzanine/forms/migrations copying mezzanine/forms/migrations/__init__.py -> build/lib/mezzanine/forms/migrations creating build/lib/mezzanine/forms/static/mezzanine/css/admin copying mezzanine/forms/static/mezzanine/css/admin/form.css -> build/lib/mezzanine/forms/static/mezzanine/css/admin copying mezzanine/forms/static/mezzanine/css/admin/form_entries.css -> build/lib/mezzanine/forms/static/mezzanine/css/admin creating build/lib/mezzanine/forms/static/mezzanine/js/admin copying mezzanine/forms/static/mezzanine/js/admin/form_entries.js -> build/lib/mezzanine/forms/static/mezzanine/js/admin creating build/lib/mezzanine/forms/templates/admin/forms copying mezzanine/forms/templates/admin/forms/change_form.html -> build/lib/mezzanine/forms/templates/admin/forms copying mezzanine/forms/templates/admin/forms/entries.html -> build/lib/mezzanine/forms/templates/admin/forms creating build/lib/mezzanine/forms/templates/email copying mezzanine/forms/templates/email/form_response.html -> build/lib/mezzanine/forms/templates/email copying mezzanine/forms/templates/email/form_response.txt -> build/lib/mezzanine/forms/templates/email copying mezzanine/forms/templates/email/form_response_copies.html -> build/lib/mezzanine/forms/templates/email copying mezzanine/forms/templates/email/form_response_copies.txt -> build/lib/mezzanine/forms/templates/email creating build/lib/mezzanine/forms/templates/pages copying mezzanine/forms/templates/pages/form.html -> build/lib/mezzanine/forms/templates/pages creating build/lib/mezzanine/galleries copying mezzanine/galleries/__init__.py -> build/lib/mezzanine/galleries copying mezzanine/galleries/admin.py -> build/lib/mezzanine/galleries copying mezzanine/galleries/models.py -> build/lib/mezzanine/galleries copying mezzanine/galleries/translation.py -> build/lib/mezzanine/galleries creating build/lib/mezzanine/galleries/fixtures copying mezzanine/galleries/fixtures/mezzanine_optional.json -> build/lib/mezzanine/galleries/fixtures creating build/lib/mezzanine/galleries/locale/ar/LC_MESSAGES copying mezzanine/galleries/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/ar/LC_MESSAGES copying mezzanine/galleries/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/ar/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/bg/LC_MESSAGES copying mezzanine/galleries/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/bg/LC_MESSAGES copying mezzanine/galleries/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/bg/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/ca/LC_MESSAGES copying mezzanine/galleries/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/ca/LC_MESSAGES copying mezzanine/galleries/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/ca/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/cs/LC_MESSAGES copying mezzanine/galleries/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/cs/LC_MESSAGES copying mezzanine/galleries/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/cs/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/da/LC_MESSAGES copying mezzanine/galleries/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/da/LC_MESSAGES copying mezzanine/galleries/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/da/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/de/LC_MESSAGES copying mezzanine/galleries/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/de/LC_MESSAGES copying mezzanine/galleries/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/de/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/en/LC_MESSAGES copying mezzanine/galleries/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/en/LC_MESSAGES copying mezzanine/galleries/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/en/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/eo/LC_MESSAGES copying mezzanine/galleries/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/eo/LC_MESSAGES copying mezzanine/galleries/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/eo/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/es/LC_MESSAGES copying mezzanine/galleries/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/es/LC_MESSAGES copying mezzanine/galleries/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/es/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/et/LC_MESSAGES copying mezzanine/galleries/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/et/LC_MESSAGES copying mezzanine/galleries/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/et/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/fa/LC_MESSAGES copying mezzanine/galleries/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/fa/LC_MESSAGES copying mezzanine/galleries/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/fa/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/fa_IR/LC_MESSAGES copying mezzanine/galleries/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/fa_IR/LC_MESSAGES copying mezzanine/galleries/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/fi/LC_MESSAGES copying mezzanine/galleries/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/fi/LC_MESSAGES copying mezzanine/galleries/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/fi/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/fr/LC_MESSAGES copying mezzanine/galleries/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/fr/LC_MESSAGES copying mezzanine/galleries/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/fr/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/hr_HR/LC_MESSAGES copying mezzanine/galleries/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/hr_HR/LC_MESSAGES copying mezzanine/galleries/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/hu/LC_MESSAGES copying mezzanine/galleries/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/hu/LC_MESSAGES copying mezzanine/galleries/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/hu/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/id_ID/LC_MESSAGES copying mezzanine/galleries/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/id_ID/LC_MESSAGES copying mezzanine/galleries/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/is_IS/LC_MESSAGES copying mezzanine/galleries/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/is_IS/LC_MESSAGES copying mezzanine/galleries/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/it/LC_MESSAGES copying mezzanine/galleries/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/it/LC_MESSAGES copying mezzanine/galleries/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/it/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/ja/LC_MESSAGES copying mezzanine/galleries/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/ja/LC_MESSAGES copying mezzanine/galleries/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/ja/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/ko/LC_MESSAGES copying mezzanine/galleries/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/ko/LC_MESSAGES copying mezzanine/galleries/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/ko/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/lv/LC_MESSAGES copying mezzanine/galleries/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/lv/LC_MESSAGES copying mezzanine/galleries/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/lv/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/nb/LC_MESSAGES copying mezzanine/galleries/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/nb/LC_MESSAGES copying mezzanine/galleries/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/nb/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/nl/LC_MESSAGES copying mezzanine/galleries/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/nl/LC_MESSAGES copying mezzanine/galleries/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/nl/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/pap/LC_MESSAGES copying mezzanine/galleries/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/pap/LC_MESSAGES copying mezzanine/galleries/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/pap/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/pl/LC_MESSAGES copying mezzanine/galleries/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/pl/LC_MESSAGES copying mezzanine/galleries/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/pl/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/pt_BR/LC_MESSAGES copying mezzanine/galleries/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/pt_BR/LC_MESSAGES copying mezzanine/galleries/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/pt_PT/LC_MESSAGES copying mezzanine/galleries/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/pt_PT/LC_MESSAGES copying mezzanine/galleries/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/ru/LC_MESSAGES copying mezzanine/galleries/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/ru/LC_MESSAGES copying mezzanine/galleries/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/ru/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/sk/LC_MESSAGES copying mezzanine/galleries/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/sk/LC_MESSAGES copying mezzanine/galleries/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/sk/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/sr_Latn/LC_MESSAGES copying mezzanine/galleries/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/sr_Latn/LC_MESSAGES copying mezzanine/galleries/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/sv/LC_MESSAGES copying mezzanine/galleries/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/sv/LC_MESSAGES copying mezzanine/galleries/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/sv/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/tr/LC_MESSAGES copying mezzanine/galleries/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/tr/LC_MESSAGES copying mezzanine/galleries/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/tr/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/uk_UA/LC_MESSAGES copying mezzanine/galleries/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/uk_UA/LC_MESSAGES copying mezzanine/galleries/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/vi_VN/LC_MESSAGES copying mezzanine/galleries/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/vi_VN/LC_MESSAGES copying mezzanine/galleries/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/zh/LC_MESSAGES copying mezzanine/galleries/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/zh/LC_MESSAGES copying mezzanine/galleries/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/zh/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/zh_CN/LC_MESSAGES copying mezzanine/galleries/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/zh_CN/LC_MESSAGES copying mezzanine/galleries/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/galleries/locale/zh_TW/LC_MESSAGES copying mezzanine/galleries/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/galleries/locale/zh_TW/LC_MESSAGES copying mezzanine/galleries/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/galleries/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/galleries/migrations copying mezzanine/galleries/migrations/0001_initial.py -> build/lib/mezzanine/galleries/migrations copying mezzanine/galleries/migrations/0002_auto_20141227_0224.py -> build/lib/mezzanine/galleries/migrations copying mezzanine/galleries/migrations/__init__.py -> build/lib/mezzanine/galleries/migrations creating build/lib/mezzanine/galleries/static/mezzanine/css copying mezzanine/galleries/static/mezzanine/css/magnific-popup.css -> build/lib/mezzanine/galleries/static/mezzanine/css creating build/lib/mezzanine/galleries/static/mezzanine/css/admin copying mezzanine/galleries/static/mezzanine/css/admin/gallery.css -> build/lib/mezzanine/galleries/static/mezzanine/css/admin creating build/lib/mezzanine/galleries/static/mezzanine/js copying mezzanine/galleries/static/mezzanine/js/magnific-popup.js -> build/lib/mezzanine/galleries/static/mezzanine/js creating build/lib/mezzanine/galleries/templates/pages copying mezzanine/galleries/templates/pages/gallery.html -> build/lib/mezzanine/galleries/templates/pages creating build/lib/mezzanine/generic copying mezzanine/generic/__init__.py -> build/lib/mezzanine/generic copying mezzanine/generic/admin.py -> build/lib/mezzanine/generic copying mezzanine/generic/defaults.py -> build/lib/mezzanine/generic copying mezzanine/generic/fields.py -> build/lib/mezzanine/generic copying mezzanine/generic/forms.py -> build/lib/mezzanine/generic copying mezzanine/generic/managers.py -> build/lib/mezzanine/generic copying mezzanine/generic/models.py -> build/lib/mezzanine/generic copying mezzanine/generic/urls.py -> build/lib/mezzanine/generic copying mezzanine/generic/views.py -> build/lib/mezzanine/generic creating build/lib/mezzanine/generic/locale/ar/LC_MESSAGES copying mezzanine/generic/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/ar/LC_MESSAGES copying mezzanine/generic/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/ar/LC_MESSAGES creating build/lib/mezzanine/generic/locale/bg/LC_MESSAGES copying mezzanine/generic/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/bg/LC_MESSAGES copying mezzanine/generic/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/bg/LC_MESSAGES creating build/lib/mezzanine/generic/locale/ca/LC_MESSAGES copying mezzanine/generic/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/ca/LC_MESSAGES copying mezzanine/generic/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/ca/LC_MESSAGES creating build/lib/mezzanine/generic/locale/cs/LC_MESSAGES copying mezzanine/generic/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/cs/LC_MESSAGES copying mezzanine/generic/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/cs/LC_MESSAGES creating build/lib/mezzanine/generic/locale/da/LC_MESSAGES copying mezzanine/generic/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/da/LC_MESSAGES copying mezzanine/generic/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/da/LC_MESSAGES creating build/lib/mezzanine/generic/locale/de/LC_MESSAGES copying mezzanine/generic/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/de/LC_MESSAGES copying mezzanine/generic/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/de/LC_MESSAGES creating build/lib/mezzanine/generic/locale/en/LC_MESSAGES copying mezzanine/generic/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/en/LC_MESSAGES copying mezzanine/generic/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/en/LC_MESSAGES creating build/lib/mezzanine/generic/locale/eo/LC_MESSAGES copying mezzanine/generic/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/eo/LC_MESSAGES copying mezzanine/generic/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/eo/LC_MESSAGES creating build/lib/mezzanine/generic/locale/es/LC_MESSAGES copying mezzanine/generic/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/es/LC_MESSAGES copying mezzanine/generic/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/es/LC_MESSAGES creating build/lib/mezzanine/generic/locale/et/LC_MESSAGES copying mezzanine/generic/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/et/LC_MESSAGES copying mezzanine/generic/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/et/LC_MESSAGES creating build/lib/mezzanine/generic/locale/fa/LC_MESSAGES copying mezzanine/generic/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/fa/LC_MESSAGES copying mezzanine/generic/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/fa/LC_MESSAGES creating build/lib/mezzanine/generic/locale/fa_IR/LC_MESSAGES copying mezzanine/generic/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/fa_IR/LC_MESSAGES copying mezzanine/generic/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/generic/locale/fi/LC_MESSAGES copying mezzanine/generic/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/fi/LC_MESSAGES copying mezzanine/generic/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/fi/LC_MESSAGES creating build/lib/mezzanine/generic/locale/fr/LC_MESSAGES copying mezzanine/generic/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/fr/LC_MESSAGES copying mezzanine/generic/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/fr/LC_MESSAGES creating build/lib/mezzanine/generic/locale/hr_HR/LC_MESSAGES copying mezzanine/generic/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/hr_HR/LC_MESSAGES copying mezzanine/generic/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/generic/locale/hu/LC_MESSAGES copying mezzanine/generic/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/hu/LC_MESSAGES copying mezzanine/generic/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/hu/LC_MESSAGES creating build/lib/mezzanine/generic/locale/id_ID/LC_MESSAGES copying mezzanine/generic/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/id_ID/LC_MESSAGES copying mezzanine/generic/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/generic/locale/is_IS/LC_MESSAGES copying mezzanine/generic/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/is_IS/LC_MESSAGES copying mezzanine/generic/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/generic/locale/it/LC_MESSAGES copying mezzanine/generic/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/it/LC_MESSAGES copying mezzanine/generic/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/it/LC_MESSAGES creating build/lib/mezzanine/generic/locale/ja/LC_MESSAGES copying mezzanine/generic/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/ja/LC_MESSAGES copying mezzanine/generic/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/ja/LC_MESSAGES creating build/lib/mezzanine/generic/locale/ko/LC_MESSAGES copying mezzanine/generic/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/ko/LC_MESSAGES copying mezzanine/generic/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/ko/LC_MESSAGES creating build/lib/mezzanine/generic/locale/lv/LC_MESSAGES copying mezzanine/generic/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/lv/LC_MESSAGES copying mezzanine/generic/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/lv/LC_MESSAGES creating build/lib/mezzanine/generic/locale/nb/LC_MESSAGES copying mezzanine/generic/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/nb/LC_MESSAGES copying mezzanine/generic/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/nb/LC_MESSAGES creating build/lib/mezzanine/generic/locale/nl/LC_MESSAGES copying mezzanine/generic/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/nl/LC_MESSAGES copying mezzanine/generic/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/nl/LC_MESSAGES creating build/lib/mezzanine/generic/locale/pap/LC_MESSAGES copying mezzanine/generic/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/pap/LC_MESSAGES copying mezzanine/generic/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/pap/LC_MESSAGES creating build/lib/mezzanine/generic/locale/pl/LC_MESSAGES copying mezzanine/generic/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/pl/LC_MESSAGES copying mezzanine/generic/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/pl/LC_MESSAGES creating build/lib/mezzanine/generic/locale/pt_BR/LC_MESSAGES copying mezzanine/generic/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/pt_BR/LC_MESSAGES copying mezzanine/generic/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/generic/locale/pt_PT/LC_MESSAGES copying mezzanine/generic/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/pt_PT/LC_MESSAGES copying mezzanine/generic/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/generic/locale/ru/LC_MESSAGES copying mezzanine/generic/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/ru/LC_MESSAGES copying mezzanine/generic/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/ru/LC_MESSAGES creating build/lib/mezzanine/generic/locale/sk/LC_MESSAGES copying mezzanine/generic/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/sk/LC_MESSAGES copying mezzanine/generic/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/sk/LC_MESSAGES creating build/lib/mezzanine/generic/locale/sr_Latn/LC_MESSAGES copying mezzanine/generic/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/sr_Latn/LC_MESSAGES copying mezzanine/generic/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/generic/locale/sv/LC_MESSAGES copying mezzanine/generic/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/sv/LC_MESSAGES copying mezzanine/generic/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/sv/LC_MESSAGES creating build/lib/mezzanine/generic/locale/tr/LC_MESSAGES copying mezzanine/generic/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/tr/LC_MESSAGES copying mezzanine/generic/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/tr/LC_MESSAGES creating build/lib/mezzanine/generic/locale/uk_UA/LC_MESSAGES copying mezzanine/generic/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/uk_UA/LC_MESSAGES copying mezzanine/generic/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/generic/locale/vi_VN/LC_MESSAGES copying mezzanine/generic/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/vi_VN/LC_MESSAGES copying mezzanine/generic/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/generic/locale/zh/LC_MESSAGES copying mezzanine/generic/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/zh/LC_MESSAGES copying mezzanine/generic/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/zh/LC_MESSAGES creating build/lib/mezzanine/generic/locale/zh_CN/LC_MESSAGES copying mezzanine/generic/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/zh_CN/LC_MESSAGES copying mezzanine/generic/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/generic/locale/zh_TW/LC_MESSAGES copying mezzanine/generic/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/generic/locale/zh_TW/LC_MESSAGES copying mezzanine/generic/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/generic/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/generic/migrations copying mezzanine/generic/migrations/0001_initial.py -> build/lib/mezzanine/generic/migrations copying mezzanine/generic/migrations/0002_auto_20141227_0224.py -> build/lib/mezzanine/generic/migrations copying mezzanine/generic/migrations/0003_auto_20170411_0504.py -> build/lib/mezzanine/generic/migrations copying mezzanine/generic/migrations/__init__.py -> build/lib/mezzanine/generic/migrations creating build/lib/mezzanine/generic/templates/admin/includes copying mezzanine/generic/templates/admin/includes/recent_comments.html -> build/lib/mezzanine/generic/templates/admin/includes creating build/lib/mezzanine/generic/templates/email copying mezzanine/generic/templates/email/comment_notification.html -> build/lib/mezzanine/generic/templates/email copying mezzanine/generic/templates/email/comment_notification.txt -> build/lib/mezzanine/generic/templates/email creating build/lib/mezzanine/generic/templates/generic copying mezzanine/generic/templates/generic/comments.html -> build/lib/mezzanine/generic/templates/generic creating build/lib/mezzanine/generic/templates/generic/includes copying mezzanine/generic/templates/generic/includes/comment.html -> build/lib/mezzanine/generic/templates/generic/includes copying mezzanine/generic/templates/generic/includes/comments.html -> build/lib/mezzanine/generic/templates/generic/includes copying mezzanine/generic/templates/generic/includes/disqus_comments.html -> build/lib/mezzanine/generic/templates/generic/includes copying mezzanine/generic/templates/generic/includes/disqus_counts.html -> build/lib/mezzanine/generic/templates/generic/includes copying mezzanine/generic/templates/generic/includes/disqus_sso.html -> build/lib/mezzanine/generic/templates/generic/includes copying mezzanine/generic/templates/generic/includes/rating.html -> build/lib/mezzanine/generic/templates/generic/includes creating build/lib/mezzanine/generic/templatetags copying mezzanine/generic/templatetags/__init__.py -> build/lib/mezzanine/generic/templatetags copying mezzanine/generic/templatetags/comment_tags.py -> build/lib/mezzanine/generic/templatetags copying mezzanine/generic/templatetags/disqus_tags.py -> build/lib/mezzanine/generic/templatetags copying mezzanine/generic/templatetags/keyword_tags.py -> build/lib/mezzanine/generic/templatetags copying mezzanine/generic/templatetags/rating_tags.py -> build/lib/mezzanine/generic/templatetags creating build/lib/mezzanine/mobile copying mezzanine/mobile/__init__.py -> build/lib/mezzanine/mobile copying mezzanine/mobile/models.py -> build/lib/mezzanine/mobile creating build/lib/mezzanine/pages copying mezzanine/pages/__init__.py -> build/lib/mezzanine/pages copying mezzanine/pages/admin.py -> build/lib/mezzanine/pages copying mezzanine/pages/apps.py -> build/lib/mezzanine/pages copying mezzanine/pages/checks.py -> build/lib/mezzanine/pages copying mezzanine/pages/context_processors.py -> build/lib/mezzanine/pages copying mezzanine/pages/defaults.py -> build/lib/mezzanine/pages copying mezzanine/pages/fields.py -> build/lib/mezzanine/pages copying mezzanine/pages/managers.py -> build/lib/mezzanine/pages copying mezzanine/pages/middleware.py -> build/lib/mezzanine/pages copying mezzanine/pages/models.py -> build/lib/mezzanine/pages copying mezzanine/pages/page_processors.py -> build/lib/mezzanine/pages copying mezzanine/pages/translation.py -> build/lib/mezzanine/pages copying mezzanine/pages/urls.py -> build/lib/mezzanine/pages copying mezzanine/pages/views.py -> build/lib/mezzanine/pages creating build/lib/mezzanine/pages/fixtures copying mezzanine/pages/fixtures/mezzanine_optional.json -> build/lib/mezzanine/pages/fixtures copying mezzanine/pages/fixtures/mezzanine_required.json -> build/lib/mezzanine/pages/fixtures creating build/lib/mezzanine/pages/locale/ar/LC_MESSAGES copying mezzanine/pages/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/ar/LC_MESSAGES copying mezzanine/pages/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/ar/LC_MESSAGES creating build/lib/mezzanine/pages/locale/bg/LC_MESSAGES copying mezzanine/pages/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/bg/LC_MESSAGES copying mezzanine/pages/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/bg/LC_MESSAGES creating build/lib/mezzanine/pages/locale/ca/LC_MESSAGES copying mezzanine/pages/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/ca/LC_MESSAGES copying mezzanine/pages/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/ca/LC_MESSAGES creating build/lib/mezzanine/pages/locale/cs/LC_MESSAGES copying mezzanine/pages/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/cs/LC_MESSAGES copying mezzanine/pages/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/cs/LC_MESSAGES creating build/lib/mezzanine/pages/locale/da/LC_MESSAGES copying mezzanine/pages/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/da/LC_MESSAGES copying mezzanine/pages/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/da/LC_MESSAGES creating build/lib/mezzanine/pages/locale/de/LC_MESSAGES copying mezzanine/pages/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/de/LC_MESSAGES copying mezzanine/pages/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/de/LC_MESSAGES creating build/lib/mezzanine/pages/locale/en/LC_MESSAGES copying mezzanine/pages/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/en/LC_MESSAGES copying mezzanine/pages/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/en/LC_MESSAGES creating build/lib/mezzanine/pages/locale/eo/LC_MESSAGES copying mezzanine/pages/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/eo/LC_MESSAGES copying mezzanine/pages/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/eo/LC_MESSAGES creating build/lib/mezzanine/pages/locale/es/LC_MESSAGES copying mezzanine/pages/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/es/LC_MESSAGES copying mezzanine/pages/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/es/LC_MESSAGES creating build/lib/mezzanine/pages/locale/et/LC_MESSAGES copying mezzanine/pages/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/et/LC_MESSAGES copying mezzanine/pages/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/et/LC_MESSAGES creating build/lib/mezzanine/pages/locale/fa/LC_MESSAGES copying mezzanine/pages/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/fa/LC_MESSAGES copying mezzanine/pages/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/fa/LC_MESSAGES creating build/lib/mezzanine/pages/locale/fa_IR/LC_MESSAGES copying mezzanine/pages/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/fa_IR/LC_MESSAGES copying mezzanine/pages/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/pages/locale/fi/LC_MESSAGES copying mezzanine/pages/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/fi/LC_MESSAGES copying mezzanine/pages/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/fi/LC_MESSAGES creating build/lib/mezzanine/pages/locale/fr/LC_MESSAGES copying mezzanine/pages/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/fr/LC_MESSAGES copying mezzanine/pages/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/fr/LC_MESSAGES creating build/lib/mezzanine/pages/locale/hr_HR/LC_MESSAGES copying mezzanine/pages/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/hr_HR/LC_MESSAGES copying mezzanine/pages/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/pages/locale/hu/LC_MESSAGES copying mezzanine/pages/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/hu/LC_MESSAGES copying mezzanine/pages/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/hu/LC_MESSAGES creating build/lib/mezzanine/pages/locale/id_ID/LC_MESSAGES copying mezzanine/pages/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/id_ID/LC_MESSAGES copying mezzanine/pages/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/pages/locale/is_IS/LC_MESSAGES copying mezzanine/pages/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/is_IS/LC_MESSAGES copying mezzanine/pages/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/pages/locale/it/LC_MESSAGES copying mezzanine/pages/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/it/LC_MESSAGES copying mezzanine/pages/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/it/LC_MESSAGES creating build/lib/mezzanine/pages/locale/ja/LC_MESSAGES copying mezzanine/pages/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/ja/LC_MESSAGES copying mezzanine/pages/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/ja/LC_MESSAGES creating build/lib/mezzanine/pages/locale/ko/LC_MESSAGES copying mezzanine/pages/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/ko/LC_MESSAGES copying mezzanine/pages/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/ko/LC_MESSAGES creating build/lib/mezzanine/pages/locale/lv/LC_MESSAGES copying mezzanine/pages/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/lv/LC_MESSAGES copying mezzanine/pages/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/lv/LC_MESSAGES creating build/lib/mezzanine/pages/locale/nb/LC_MESSAGES copying mezzanine/pages/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/nb/LC_MESSAGES copying mezzanine/pages/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/nb/LC_MESSAGES creating build/lib/mezzanine/pages/locale/nl/LC_MESSAGES copying mezzanine/pages/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/nl/LC_MESSAGES copying mezzanine/pages/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/nl/LC_MESSAGES creating build/lib/mezzanine/pages/locale/pap/LC_MESSAGES copying mezzanine/pages/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/pap/LC_MESSAGES copying mezzanine/pages/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/pap/LC_MESSAGES creating build/lib/mezzanine/pages/locale/pl/LC_MESSAGES copying mezzanine/pages/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/pl/LC_MESSAGES copying mezzanine/pages/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/pl/LC_MESSAGES creating build/lib/mezzanine/pages/locale/pt_BR/LC_MESSAGES copying mezzanine/pages/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/pt_BR/LC_MESSAGES copying mezzanine/pages/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/pages/locale/pt_PT/LC_MESSAGES copying mezzanine/pages/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/pt_PT/LC_MESSAGES copying mezzanine/pages/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/pages/locale/ru/LC_MESSAGES copying mezzanine/pages/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/ru/LC_MESSAGES copying mezzanine/pages/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/ru/LC_MESSAGES creating build/lib/mezzanine/pages/locale/sk/LC_MESSAGES copying mezzanine/pages/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/sk/LC_MESSAGES copying mezzanine/pages/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/sk/LC_MESSAGES creating build/lib/mezzanine/pages/locale/sr_Latn/LC_MESSAGES copying mezzanine/pages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/sr_Latn/LC_MESSAGES copying mezzanine/pages/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/pages/locale/sv/LC_MESSAGES copying mezzanine/pages/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/sv/LC_MESSAGES copying mezzanine/pages/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/sv/LC_MESSAGES creating build/lib/mezzanine/pages/locale/tr/LC_MESSAGES copying mezzanine/pages/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/tr/LC_MESSAGES copying mezzanine/pages/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/tr/LC_MESSAGES creating build/lib/mezzanine/pages/locale/uk_UA/LC_MESSAGES copying mezzanine/pages/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/uk_UA/LC_MESSAGES copying mezzanine/pages/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/pages/locale/vi_VN/LC_MESSAGES copying mezzanine/pages/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/vi_VN/LC_MESSAGES copying mezzanine/pages/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/pages/locale/zh/LC_MESSAGES copying mezzanine/pages/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/zh/LC_MESSAGES copying mezzanine/pages/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/zh/LC_MESSAGES creating build/lib/mezzanine/pages/locale/zh_CN/LC_MESSAGES copying mezzanine/pages/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/zh_CN/LC_MESSAGES copying mezzanine/pages/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/pages/locale/zh_TW/LC_MESSAGES copying mezzanine/pages/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/pages/locale/zh_TW/LC_MESSAGES copying mezzanine/pages/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/pages/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/pages/migrations copying mezzanine/pages/migrations/0001_initial.py -> build/lib/mezzanine/pages/migrations copying mezzanine/pages/migrations/0002_auto_20141227_0224.py -> build/lib/mezzanine/pages/migrations copying mezzanine/pages/migrations/0003_auto_20150527_1555.py -> build/lib/mezzanine/pages/migrations copying mezzanine/pages/migrations/0004_auto_20170411_0504.py -> build/lib/mezzanine/pages/migrations copying mezzanine/pages/migrations/__init__.py -> build/lib/mezzanine/pages/migrations creating build/lib/mezzanine/pages/static/mezzanine/css/admin copying mezzanine/pages/static/mezzanine/css/admin/page_tree.css -> build/lib/mezzanine/pages/static/mezzanine/css/admin creating build/lib/mezzanine/pages/static/mezzanine/js/admin copying mezzanine/pages/static/mezzanine/js/admin/jquery.mjs.nestedSortable.js -> build/lib/mezzanine/pages/static/mezzanine/js/admin copying mezzanine/pages/static/mezzanine/js/admin/page_tree.js -> build/lib/mezzanine/pages/static/mezzanine/js/admin creating build/lib/mezzanine/pages/templates/admin/pages/link copying mezzanine/pages/templates/admin/pages/link/change_form.html -> build/lib/mezzanine/pages/templates/admin/pages/link creating build/lib/mezzanine/pages/templates/admin/pages/page copying mezzanine/pages/templates/admin/pages/page/change_list.html -> build/lib/mezzanine/pages/templates/admin/pages/page copying mezzanine/pages/templates/admin/pages/page/delete_confirmation.html -> build/lib/mezzanine/pages/templates/admin/pages/page creating build/lib/mezzanine/pages/templates/pages copying mezzanine/pages/templates/pages/index.html -> build/lib/mezzanine/pages/templates/pages copying mezzanine/pages/templates/pages/page.html -> build/lib/mezzanine/pages/templates/pages copying mezzanine/pages/templates/pages/richtextpage.html -> build/lib/mezzanine/pages/templates/pages creating build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/admin.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/breadcrumb.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/dropdown.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/footer.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/footer_tree.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/mobile.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/primary.html -> build/lib/mezzanine/pages/templates/pages/menus copying mezzanine/pages/templates/pages/menus/tree.html -> build/lib/mezzanine/pages/templates/pages/menus creating build/lib/mezzanine/pages/templatetags copying mezzanine/pages/templatetags/__init__.py -> build/lib/mezzanine/pages/templatetags copying mezzanine/pages/templatetags/pages_tags.py -> build/lib/mezzanine/pages/templatetags creating build/lib/mezzanine/project_template copying mezzanine/project_template/.gitignore -> build/lib/mezzanine/project_template copying mezzanine/project_template/.hgignore -> build/lib/mezzanine/project_template copying mezzanine/project_template/__init__.py -> build/lib/mezzanine/project_template copying mezzanine/project_template/manage.py -> build/lib/mezzanine/project_template creating build/lib/mezzanine/project_template/project_name copying mezzanine/project_template/project_name/__init__.py -> build/lib/mezzanine/project_template/project_name copying mezzanine/project_template/project_name/local_settings.py.template -> build/lib/mezzanine/project_template/project_name copying mezzanine/project_template/project_name/settings.py -> build/lib/mezzanine/project_template/project_name copying mezzanine/project_template/project_name/urls.py -> build/lib/mezzanine/project_template/project_name copying mezzanine/project_template/project_name/wsgi.py -> build/lib/mezzanine/project_template/project_name creating build/lib/mezzanine/template copying mezzanine/template/__init__.py -> build/lib/mezzanine/template copying mezzanine/template/loader_tags.py -> build/lib/mezzanine/template creating build/lib/mezzanine/template/loaders copying mezzanine/template/loaders/__init__.py -> build/lib/mezzanine/template/loaders copying mezzanine/template/loaders/host_themes.py -> build/lib/mezzanine/template/loaders creating build/lib/mezzanine/twitter copying mezzanine/twitter/__init__.py -> build/lib/mezzanine/twitter copying mezzanine/twitter/admin.py -> build/lib/mezzanine/twitter copying mezzanine/twitter/apps.py -> build/lib/mezzanine/twitter copying mezzanine/twitter/checks.py -> build/lib/mezzanine/twitter copying mezzanine/twitter/defaults.py -> build/lib/mezzanine/twitter copying mezzanine/twitter/managers.py -> build/lib/mezzanine/twitter copying mezzanine/twitter/models.py -> build/lib/mezzanine/twitter creating build/lib/mezzanine/twitter/locale/ar/LC_MESSAGES copying mezzanine/twitter/locale/ar/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/ar/LC_MESSAGES copying mezzanine/twitter/locale/ar/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/ar/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/bg/LC_MESSAGES copying mezzanine/twitter/locale/bg/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/bg/LC_MESSAGES copying mezzanine/twitter/locale/bg/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/bg/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/ca/LC_MESSAGES copying mezzanine/twitter/locale/ca/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/ca/LC_MESSAGES copying mezzanine/twitter/locale/ca/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/ca/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/cs/LC_MESSAGES copying mezzanine/twitter/locale/cs/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/cs/LC_MESSAGES copying mezzanine/twitter/locale/cs/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/cs/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/da/LC_MESSAGES copying mezzanine/twitter/locale/da/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/da/LC_MESSAGES copying mezzanine/twitter/locale/da/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/da/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/de/LC_MESSAGES copying mezzanine/twitter/locale/de/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/de/LC_MESSAGES copying mezzanine/twitter/locale/de/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/de/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/en/LC_MESSAGES copying mezzanine/twitter/locale/en/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/en/LC_MESSAGES copying mezzanine/twitter/locale/en/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/en/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/eo/LC_MESSAGES copying mezzanine/twitter/locale/eo/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/eo/LC_MESSAGES copying mezzanine/twitter/locale/eo/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/eo/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/es/LC_MESSAGES copying mezzanine/twitter/locale/es/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/es/LC_MESSAGES copying mezzanine/twitter/locale/es/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/es/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/et/LC_MESSAGES copying mezzanine/twitter/locale/et/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/et/LC_MESSAGES copying mezzanine/twitter/locale/et/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/et/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/fa/LC_MESSAGES copying mezzanine/twitter/locale/fa/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/fa/LC_MESSAGES copying mezzanine/twitter/locale/fa/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/fa/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/fa_IR/LC_MESSAGES copying mezzanine/twitter/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/fa_IR/LC_MESSAGES copying mezzanine/twitter/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/fa_IR/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/fi/LC_MESSAGES copying mezzanine/twitter/locale/fi/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/fi/LC_MESSAGES copying mezzanine/twitter/locale/fi/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/fi/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/fr/LC_MESSAGES copying mezzanine/twitter/locale/fr/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/fr/LC_MESSAGES copying mezzanine/twitter/locale/fr/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/fr/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/hr_HR/LC_MESSAGES copying mezzanine/twitter/locale/hr_HR/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/hr_HR/LC_MESSAGES copying mezzanine/twitter/locale/hr_HR/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/hr_HR/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/hu/LC_MESSAGES copying mezzanine/twitter/locale/hu/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/hu/LC_MESSAGES copying mezzanine/twitter/locale/hu/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/hu/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/id_ID/LC_MESSAGES copying mezzanine/twitter/locale/id_ID/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/id_ID/LC_MESSAGES copying mezzanine/twitter/locale/id_ID/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/id_ID/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/is_IS/LC_MESSAGES copying mezzanine/twitter/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/is_IS/LC_MESSAGES copying mezzanine/twitter/locale/is_IS/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/is_IS/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/it/LC_MESSAGES copying mezzanine/twitter/locale/it/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/it/LC_MESSAGES copying mezzanine/twitter/locale/it/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/it/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/ja/LC_MESSAGES copying mezzanine/twitter/locale/ja/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/ja/LC_MESSAGES copying mezzanine/twitter/locale/ja/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/ja/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/ko/LC_MESSAGES copying mezzanine/twitter/locale/ko/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/ko/LC_MESSAGES copying mezzanine/twitter/locale/ko/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/ko/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/lv/LC_MESSAGES copying mezzanine/twitter/locale/lv/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/lv/LC_MESSAGES copying mezzanine/twitter/locale/lv/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/lv/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/nb/LC_MESSAGES copying mezzanine/twitter/locale/nb/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/nb/LC_MESSAGES copying mezzanine/twitter/locale/nb/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/nb/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/nl/LC_MESSAGES copying mezzanine/twitter/locale/nl/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/nl/LC_MESSAGES copying mezzanine/twitter/locale/nl/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/nl/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/pap/LC_MESSAGES copying mezzanine/twitter/locale/pap/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/pap/LC_MESSAGES copying mezzanine/twitter/locale/pap/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/pap/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/pl/LC_MESSAGES copying mezzanine/twitter/locale/pl/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/pl/LC_MESSAGES copying mezzanine/twitter/locale/pl/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/pl/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/pt_BR/LC_MESSAGES copying mezzanine/twitter/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/pt_BR/LC_MESSAGES copying mezzanine/twitter/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/pt_BR/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/pt_PT/LC_MESSAGES copying mezzanine/twitter/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/pt_PT/LC_MESSAGES copying mezzanine/twitter/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/pt_PT/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/ru/LC_MESSAGES copying mezzanine/twitter/locale/ru/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/ru/LC_MESSAGES copying mezzanine/twitter/locale/ru/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/ru/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/sk/LC_MESSAGES copying mezzanine/twitter/locale/sk/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/sk/LC_MESSAGES copying mezzanine/twitter/locale/sk/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/sk/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/sr_Latn/LC_MESSAGES copying mezzanine/twitter/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/sr_Latn/LC_MESSAGES copying mezzanine/twitter/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/sr_Latn/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/sv/LC_MESSAGES copying mezzanine/twitter/locale/sv/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/sv/LC_MESSAGES copying mezzanine/twitter/locale/sv/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/sv/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/tr/LC_MESSAGES copying mezzanine/twitter/locale/tr/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/tr/LC_MESSAGES copying mezzanine/twitter/locale/tr/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/tr/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/uk_UA/LC_MESSAGES copying mezzanine/twitter/locale/uk_UA/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/uk_UA/LC_MESSAGES copying mezzanine/twitter/locale/uk_UA/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/uk_UA/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/vi_VN/LC_MESSAGES copying mezzanine/twitter/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/vi_VN/LC_MESSAGES copying mezzanine/twitter/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/vi_VN/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/zh/LC_MESSAGES copying mezzanine/twitter/locale/zh/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/zh/LC_MESSAGES copying mezzanine/twitter/locale/zh/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/zh/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/zh_CN/LC_MESSAGES copying mezzanine/twitter/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/zh_CN/LC_MESSAGES copying mezzanine/twitter/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/zh_CN/LC_MESSAGES creating build/lib/mezzanine/twitter/locale/zh_TW/LC_MESSAGES copying mezzanine/twitter/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/mezzanine/twitter/locale/zh_TW/LC_MESSAGES copying mezzanine/twitter/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/mezzanine/twitter/locale/zh_TW/LC_MESSAGES creating build/lib/mezzanine/twitter/management copying mezzanine/twitter/management/__init__.py -> build/lib/mezzanine/twitter/management creating build/lib/mezzanine/twitter/management/commands copying mezzanine/twitter/management/commands/__init__.py -> build/lib/mezzanine/twitter/management/commands copying mezzanine/twitter/management/commands/poll_twitter.py -> build/lib/mezzanine/twitter/management/commands creating build/lib/mezzanine/twitter/migrations copying mezzanine/twitter/migrations/0001_initial.py -> build/lib/mezzanine/twitter/migrations copying mezzanine/twitter/migrations/__init__.py -> build/lib/mezzanine/twitter/migrations creating build/lib/mezzanine/twitter/templates/twitter copying mezzanine/twitter/templates/twitter/tweets.html -> build/lib/mezzanine/twitter/templates/twitter creating build/lib/mezzanine/twitter/templatetags copying mezzanine/twitter/templatetags/__init__.py -> build/lib/mezzanine/twitter/templatetags copying mezzanine/twitter/templatetags/twitter_tags.py -> build/lib/mezzanine/twitter/templatetags creating build/lib/mezzanine/utils copying mezzanine/utils/__init__.py -> build/lib/mezzanine/utils copying mezzanine/utils/admin.py -> build/lib/mezzanine/utils copying mezzanine/utils/cache.py -> build/lib/mezzanine/utils copying mezzanine/utils/conf.py -> build/lib/mezzanine/utils copying mezzanine/utils/deprecation.py -> build/lib/mezzanine/utils copying mezzanine/utils/docs.py -> build/lib/mezzanine/utils copying mezzanine/utils/email.py -> build/lib/mezzanine/utils copying mezzanine/utils/html.py -> build/lib/mezzanine/utils copying mezzanine/utils/importing.py -> build/lib/mezzanine/utils copying mezzanine/utils/models.py -> build/lib/mezzanine/utils copying mezzanine/utils/sites.py -> build/lib/mezzanine/utils copying mezzanine/utils/static.py -> build/lib/mezzanine/utils copying mezzanine/utils/tests.py -> build/lib/mezzanine/utils copying mezzanine/utils/timezone.py -> build/lib/mezzanine/utils copying mezzanine/utils/urls.py -> build/lib/mezzanine/utils copying mezzanine/utils/views.py -> build/lib/mezzanine/utils installing to build/bdist.netbsd-9.0-amd64/wheel running install running install_lib creating build/bdist.netbsd-9.0-amd64/wheel creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine copying build/lib/mezzanine/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine copying build/lib/mezzanine/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts copying build/lib/mezzanine/accounts/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts copying build/lib/mezzanine/accounts/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts copying build/lib/mezzanine/accounts/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts copying build/lib/mezzanine/accounts/forms.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts copying build/lib/mezzanine/accounts/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts copying build/lib/mezzanine/accounts/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts copying build/lib/mezzanine/accounts/views.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ar/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ar/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/bg/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/bg/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ca/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ca/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/cs/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/cs/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/da/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/da/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/de/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/de/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/en/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/en/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/eo/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/eo/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/es/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/es/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/et/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/et/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fa/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fa/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fi/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fi/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/fr/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fr/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/hu/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/hu/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/it/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/it/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ja/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ja/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ko/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ko/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/lv/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/lv/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/nb/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/nb/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/nl/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/nl/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pap/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pap/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pl/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pl/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/ru/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ru/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/sk/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/sk/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/sv/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/sv/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/tr/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/tr/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/zh/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/zh/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/accounts/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/templates/accounts copying build/lib/mezzanine/accounts/templates/accounts/account_form.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts copying build/lib/mezzanine/accounts/templates/accounts/account_login.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts copying build/lib/mezzanine/accounts/templates/accounts/account_password_reset.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts copying build/lib/mezzanine/accounts/templates/accounts/account_profile.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts copying build/lib/mezzanine/accounts/templates/accounts/account_profile_update.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts copying build/lib/mezzanine/accounts/templates/accounts/account_signup.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/templates/accounts/includes copying build/lib/mezzanine/accounts/templates/accounts/includes/user_panel.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts/includes copying build/lib/mezzanine/accounts/templates/accounts/includes/user_panel_nav.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/accounts/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/templates/admin copying build/lib/mezzanine/accounts/templates/admin/profile_inline.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/account_approve.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/account_approve.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/account_approve_subject.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/account_approved.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/account_approved.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/account_approved_subject.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/password_reset_verify.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/password_reset_verify.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/password_reset_verify_subject.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/signup_verify.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/signup_verify.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email copying build/lib/mezzanine/accounts/templates/email/signup_verify_subject.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templates/email creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/accounts/templatetags copying build/lib/mezzanine/accounts/templatetags/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templatetags copying build/lib/mezzanine/accounts/templatetags/accounts_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/accounts/templatetags creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/bin copying build/lib/mezzanine/bin/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/bin copying build/lib/mezzanine/bin/mezzanine_project.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/bin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/bin/management copying build/lib/mezzanine/bin/management/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/bin/management creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/bin/management/commands copying build/lib/mezzanine/bin/management/commands/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/bin/management/commands copying build/lib/mezzanine/bin/management/commands/mezzanine_project.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/bin/management/commands creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog copying build/lib/mezzanine/blog/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/feeds.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/forms.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/translation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog copying build/lib/mezzanine/blog/views.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ar/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ar/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/bg/LC_MESSAGES copying build/lib/mezzanine/blog/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/bg/LC_MESSAGES copying build/lib/mezzanine/blog/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ca/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ca/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/cs/LC_MESSAGES copying build/lib/mezzanine/blog/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/cs/LC_MESSAGES copying build/lib/mezzanine/blog/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/da/LC_MESSAGES copying build/lib/mezzanine/blog/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/da/LC_MESSAGES copying build/lib/mezzanine/blog/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/de/LC_MESSAGES copying build/lib/mezzanine/blog/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/de/LC_MESSAGES copying build/lib/mezzanine/blog/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/en/LC_MESSAGES copying build/lib/mezzanine/blog/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/en/LC_MESSAGES copying build/lib/mezzanine/blog/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/eo/LC_MESSAGES copying build/lib/mezzanine/blog/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/eo/LC_MESSAGES copying build/lib/mezzanine/blog/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/es/LC_MESSAGES copying build/lib/mezzanine/blog/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/es/LC_MESSAGES copying build/lib/mezzanine/blog/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/et/LC_MESSAGES copying build/lib/mezzanine/blog/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/et/LC_MESSAGES copying build/lib/mezzanine/blog/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fa/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fa/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fi/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fi/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/fr/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fr/LC_MESSAGES copying build/lib/mezzanine/blog/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/blog/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/blog/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/hu/LC_MESSAGES copying build/lib/mezzanine/blog/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/hu/LC_MESSAGES copying build/lib/mezzanine/blog/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/blog/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/blog/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/blog/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/blog/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/it/LC_MESSAGES copying build/lib/mezzanine/blog/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/it/LC_MESSAGES copying build/lib/mezzanine/blog/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ja/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ja/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ko/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ko/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/lv/LC_MESSAGES copying build/lib/mezzanine/blog/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/lv/LC_MESSAGES copying build/lib/mezzanine/blog/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/nb/LC_MESSAGES copying build/lib/mezzanine/blog/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/nb/LC_MESSAGES copying build/lib/mezzanine/blog/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/nl/LC_MESSAGES copying build/lib/mezzanine/blog/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/nl/LC_MESSAGES copying build/lib/mezzanine/blog/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pap/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pap/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pl/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pl/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/blog/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/ru/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ru/LC_MESSAGES copying build/lib/mezzanine/blog/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/sk/LC_MESSAGES copying build/lib/mezzanine/blog/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/sk/LC_MESSAGES copying build/lib/mezzanine/blog/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/blog/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/blog/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/sv/LC_MESSAGES copying build/lib/mezzanine/blog/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/sv/LC_MESSAGES copying build/lib/mezzanine/blog/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/tr/LC_MESSAGES copying build/lib/mezzanine/blog/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/tr/LC_MESSAGES copying build/lib/mezzanine/blog/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/blog/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/blog/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/blog/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/blog/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/zh/LC_MESSAGES copying build/lib/mezzanine/blog/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/zh/LC_MESSAGES copying build/lib/mezzanine/blog/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/blog/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/blog/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/blog/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/blog/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/management copying build/lib/mezzanine/blog/management/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management copying build/lib/mezzanine/blog/management/base.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/import_blogger.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/import_blogml.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/import_posterous.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/import_rss.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/import_tumblr.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands copying build/lib/mezzanine/blog/management/commands/import_wordpress.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/management/commands creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/migrations copying build/lib/mezzanine/blog/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/migrations copying build/lib/mezzanine/blog/migrations/0002_auto_20150527_1555.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/migrations copying build/lib/mezzanine/blog/migrations/0003_auto_20170411_0504.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/migrations copying build/lib/mezzanine/blog/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/templates/admin/includes copying build/lib/mezzanine/blog/templates/admin/includes/quick_blog.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/templates/admin/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/templates/blog copying build/lib/mezzanine/blog/templates/blog/blog_post_detail.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/templates/blog copying build/lib/mezzanine/blog/templates/blog/blog_post_list.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/templates/blog creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/templates/blog/includes copying build/lib/mezzanine/blog/templates/blog/includes/filter_panel.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/templates/blog/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/blog/templatetags copying build/lib/mezzanine/blog/templatetags/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/templatetags copying build/lib/mezzanine/blog/templatetags/blog_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/blog/templatetags creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/boot copying build/lib/mezzanine/boot/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/boot copying build/lib/mezzanine/boot/lazy_admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/boot copying build/lib/mezzanine/boot/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/boot creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf copying build/lib/mezzanine/conf/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf copying build/lib/mezzanine/conf/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf copying build/lib/mezzanine/conf/context_processors.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf copying build/lib/mezzanine/conf/forms.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf copying build/lib/mezzanine/conf/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf copying build/lib/mezzanine/conf/translation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ar/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ar/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/bg/LC_MESSAGES copying build/lib/mezzanine/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/bg/LC_MESSAGES copying build/lib/mezzanine/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ca/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ca/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/cs/LC_MESSAGES copying build/lib/mezzanine/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/cs/LC_MESSAGES copying build/lib/mezzanine/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/da/LC_MESSAGES copying build/lib/mezzanine/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/da/LC_MESSAGES copying build/lib/mezzanine/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/de/LC_MESSAGES copying build/lib/mezzanine/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/de/LC_MESSAGES copying build/lib/mezzanine/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/en/LC_MESSAGES copying build/lib/mezzanine/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/en/LC_MESSAGES copying build/lib/mezzanine/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/eo/LC_MESSAGES copying build/lib/mezzanine/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/eo/LC_MESSAGES copying build/lib/mezzanine/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/es/LC_MESSAGES copying build/lib/mezzanine/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/es/LC_MESSAGES copying build/lib/mezzanine/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/et/LC_MESSAGES copying build/lib/mezzanine/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/et/LC_MESSAGES copying build/lib/mezzanine/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fa/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fa/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fi/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fi/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/fr/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fr/LC_MESSAGES copying build/lib/mezzanine/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/conf/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/conf/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/hu/LC_MESSAGES copying build/lib/mezzanine/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/hu/LC_MESSAGES copying build/lib/mezzanine/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/conf/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/conf/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/conf/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/conf/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/it/LC_MESSAGES copying build/lib/mezzanine/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/it/LC_MESSAGES copying build/lib/mezzanine/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ja/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ja/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ko/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ko/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/lv/LC_MESSAGES copying build/lib/mezzanine/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/lv/LC_MESSAGES copying build/lib/mezzanine/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/nb/LC_MESSAGES copying build/lib/mezzanine/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/nb/LC_MESSAGES copying build/lib/mezzanine/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/nl/LC_MESSAGES copying build/lib/mezzanine/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/nl/LC_MESSAGES copying build/lib/mezzanine/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pap/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pap/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pl/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pl/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/conf/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/ru/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ru/LC_MESSAGES copying build/lib/mezzanine/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/sk/LC_MESSAGES copying build/lib/mezzanine/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/sk/LC_MESSAGES copying build/lib/mezzanine/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/sv/LC_MESSAGES copying build/lib/mezzanine/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/sv/LC_MESSAGES copying build/lib/mezzanine/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/tr/LC_MESSAGES copying build/lib/mezzanine/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/tr/LC_MESSAGES copying build/lib/mezzanine/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/conf/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/conf/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/conf/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/conf/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/zh/LC_MESSAGES copying build/lib/mezzanine/conf/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/zh/LC_MESSAGES copying build/lib/mezzanine/conf/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/conf/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/conf/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/conf/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/conf/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/migrations copying build/lib/mezzanine/conf/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/migrations copying build/lib/mezzanine/conf/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/static creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/static/mezzanine creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/static/mezzanine/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/static/mezzanine/css/admin copying build/lib/mezzanine/conf/static/mezzanine/css/admin/settings.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/static/mezzanine/css/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/static/mezzanine/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/static/mezzanine/js/admin copying build/lib/mezzanine/conf/static/mezzanine/js/admin/tabbed_translatable_settings.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/static/mezzanine/js/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/templates/admin/conf creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/conf/templates/admin/conf/setting copying build/lib/mezzanine/conf/templates/admin/conf/setting/change_list.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/conf/templates/admin/conf/setting creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core copying build/lib/mezzanine/core/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/apps.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/auth_backends.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/checks.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/exceptions.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/fields.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/forms.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/managers.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/middleware.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/request.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/sitemaps.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/translation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core copying build/lib/mezzanine/core/views.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ar/LC_MESSAGES copying build/lib/mezzanine/core/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ar/LC_MESSAGES copying build/lib/mezzanine/core/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/bg/LC_MESSAGES copying build/lib/mezzanine/core/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/bg/LC_MESSAGES copying build/lib/mezzanine/core/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ca/LC_MESSAGES copying build/lib/mezzanine/core/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ca/LC_MESSAGES copying build/lib/mezzanine/core/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/cs/LC_MESSAGES copying build/lib/mezzanine/core/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/cs/LC_MESSAGES copying build/lib/mezzanine/core/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/da/LC_MESSAGES copying build/lib/mezzanine/core/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/da/LC_MESSAGES copying build/lib/mezzanine/core/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/de/LC_MESSAGES copying build/lib/mezzanine/core/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/de/LC_MESSAGES copying build/lib/mezzanine/core/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/en/LC_MESSAGES copying build/lib/mezzanine/core/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/en/LC_MESSAGES copying build/lib/mezzanine/core/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/eo/LC_MESSAGES copying build/lib/mezzanine/core/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/eo/LC_MESSAGES copying build/lib/mezzanine/core/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/es/LC_MESSAGES copying build/lib/mezzanine/core/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/es/LC_MESSAGES copying build/lib/mezzanine/core/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/et/LC_MESSAGES copying build/lib/mezzanine/core/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/et/LC_MESSAGES copying build/lib/mezzanine/core/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fa/LC_MESSAGES copying build/lib/mezzanine/core/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fa/LC_MESSAGES copying build/lib/mezzanine/core/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/core/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/core/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fi/LC_MESSAGES copying build/lib/mezzanine/core/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fi/LC_MESSAGES copying build/lib/mezzanine/core/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/fr/LC_MESSAGES copying build/lib/mezzanine/core/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fr/LC_MESSAGES copying build/lib/mezzanine/core/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/core/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/core/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/hu/LC_MESSAGES copying build/lib/mezzanine/core/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/hu/LC_MESSAGES copying build/lib/mezzanine/core/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/core/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/core/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/core/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/core/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/it/LC_MESSAGES copying build/lib/mezzanine/core/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/it/LC_MESSAGES copying build/lib/mezzanine/core/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ja/LC_MESSAGES copying build/lib/mezzanine/core/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ja/LC_MESSAGES copying build/lib/mezzanine/core/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ko/LC_MESSAGES copying build/lib/mezzanine/core/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ko/LC_MESSAGES copying build/lib/mezzanine/core/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/lv/LC_MESSAGES copying build/lib/mezzanine/core/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/lv/LC_MESSAGES copying build/lib/mezzanine/core/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/nb/LC_MESSAGES copying build/lib/mezzanine/core/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/nb/LC_MESSAGES copying build/lib/mezzanine/core/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/nl/LC_MESSAGES copying build/lib/mezzanine/core/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/nl/LC_MESSAGES copying build/lib/mezzanine/core/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pap/LC_MESSAGES copying build/lib/mezzanine/core/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pap/LC_MESSAGES copying build/lib/mezzanine/core/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pl/LC_MESSAGES copying build/lib/mezzanine/core/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pl/LC_MESSAGES copying build/lib/mezzanine/core/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/core/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/core/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/core/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/core/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/ru/LC_MESSAGES copying build/lib/mezzanine/core/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ru/LC_MESSAGES copying build/lib/mezzanine/core/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/sk/LC_MESSAGES copying build/lib/mezzanine/core/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/sk/LC_MESSAGES copying build/lib/mezzanine/core/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/core/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/core/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/sv/LC_MESSAGES copying build/lib/mezzanine/core/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/sv/LC_MESSAGES copying build/lib/mezzanine/core/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/tr/LC_MESSAGES copying build/lib/mezzanine/core/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/tr/LC_MESSAGES copying build/lib/mezzanine/core/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/core/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/core/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/core/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/core/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/zh/LC_MESSAGES copying build/lib/mezzanine/core/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/zh/LC_MESSAGES copying build/lib/mezzanine/core/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/core/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/core/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/core/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/core/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/management copying build/lib/mezzanine/core/management/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/management creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/management/commands copying build/lib/mezzanine/core/management/commands/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/management/commands copying build/lib/mezzanine/core/management/commands/collecttemplates.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/management/commands copying build/lib/mezzanine/core/management/commands/createdb.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/management/commands copying build/lib/mezzanine/core/management/commands/runserver.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/management/commands creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/migrations copying build/lib/mezzanine/core/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/migrations copying build/lib/mezzanine/core/migrations/0002_auto_20150414_2140.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/migrations copying build/lib/mezzanine/core/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static copying build/lib/mezzanine/core/static/robots.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/admin/img creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/admin/img/admin copying build/lib/mezzanine/core/static/admin/img/admin/README -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/admin/img/admin copying build/lib/mezzanine/core/static/admin/img/admin/arrow-down.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/admin/img/admin copying build/lib/mezzanine/core/static/admin/img/admin/arrow-up.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/admin/img/admin copying build/lib/mezzanine/core/static/admin/img/admin/icon_deletelink.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/admin/img/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/admin/js copying build/lib/mezzanine/core/static/admin/js/collapse.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/admin/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/css copying build/lib/mezzanine/core/static/css/bootstrap-rtl.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/css copying build/lib/mezzanine/core/static/css/bootstrap-theme.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/css copying build/lib/mezzanine/core/static/css/bootstrap.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/css copying build/lib/mezzanine/core/static/css/mezzanine.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/fonts copying build/lib/mezzanine/core/static/fonts/glyphicons-halflings-regular.eot -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/fonts copying build/lib/mezzanine/core/static/fonts/glyphicons-halflings-regular.svg -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/fonts copying build/lib/mezzanine/core/static/fonts/glyphicons-halflings-regular.ttf -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/fonts copying build/lib/mezzanine/core/static/fonts/glyphicons-halflings-regular.woff -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/fonts creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/img copying build/lib/mezzanine/core/static/img/favicon.ico -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/img creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/js copying build/lib/mezzanine/core/static/js/bootstrap-extras.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/js copying build/lib/mezzanine/core/static/js/bootstrap.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/js copying build/lib/mezzanine/core/static/js/html5shiv.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/js copying build/lib/mezzanine/core/static/js/respond.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/chosen copying build/lib/mezzanine/core/static/mezzanine/chosen/chosen-0.9.12.jquery.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/chosen copying build/lib/mezzanine/core/static/mezzanine/chosen/chosen-sprite-dark.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/chosen copying build/lib/mezzanine/core/static/mezzanine/chosen/chosen-sprite.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/chosen copying build/lib/mezzanine/core/static/mezzanine/chosen/chosen.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/chosen creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/css copying build/lib/mezzanine/core/static/mezzanine/css/editable.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css copying build/lib/mezzanine/core/static/mezzanine/css/tinymce.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/css/admin copying build/lib/mezzanine/core/static/mezzanine/css/admin/dashboard.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/admin copying build/lib/mezzanine/core/static/mezzanine/css/admin/global.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/admin copying build/lib/mezzanine/core/static/mezzanine/css/admin/rtl.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/admin copying build/lib/mezzanine/core/static/mezzanine/css/admin/tabbed_translation_fields.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/css/smoothness copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/jquery-ui.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/jquery-ui.min.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_flat_75_ffffff_40x100.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_75_dadada_1x400.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_222222_256x240.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_2e83ff_256x240.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_454545_256x240.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_888888_256x240.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images copying build/lib/mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_cd0a0a_256x240.png -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/css/smoothness/images creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/img copying build/lib/mezzanine/core/static/mezzanine/img/loadingAnimation.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/img creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/editable.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/jquery-3.4.1.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/jquery-ui-1.12.1.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/jquery.form.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/jquery.tools.overlay.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/jquery.tools.toolbox.expose.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js copying build/lib/mezzanine/core/static/mezzanine/js/tinymce_setup.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/js/admin copying build/lib/mezzanine/core/static/mezzanine/js/admin/ajax_csrf.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js/admin copying build/lib/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js/admin copying build/lib/mezzanine/core/static/mezzanine/js/admin/keywords_field.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js/admin copying build/lib/mezzanine/core/static/mezzanine/js/admin/login.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js/admin copying build/lib/mezzanine/core/static/mezzanine/js/admin/navigation.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js/admin copying build/lib/mezzanine/core/static/mezzanine/js/admin/tabbed_translation_fields.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/js/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce copying build/lib/mezzanine/core/static/mezzanine/tinymce/jquery.tinymce.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce copying build/lib/mezzanine/core/static/mezzanine/tinymce/license.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce copying build/lib/mezzanine/core/static/mezzanine/tinymce/tinymce.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce copying build/lib/mezzanine/core/static/mezzanine/tinymce/tinymce.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/ar.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/ca.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/cs.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/da.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/de.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/es.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/et.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/fa.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/fa_IR.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/fi.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/fr_FR.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/hr.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/hu_HU.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/id.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/is_IS.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/it.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/ja.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/ko_KR.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/lv.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/nb_NO.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/nl.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/pl.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/pt_BR.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/pt_PT.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/ru.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/sk.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/sr.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/sv_SE.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/tr.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/uk_UA.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/vi.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/zh_CN.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs copying build/lib/mezzanine/core/static/mezzanine/tinymce/langs/zh_TW.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/langs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/advlist copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/advlist/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/advlist creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/anchor copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/anchor/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/anchor creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/autolink copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autolink/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/autolink creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/autoresize copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autoresize/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/autoresize creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/autosave copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/autosave/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/autosave creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/bbcode copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/bbcode/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/bbcode creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/charmap copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/charmap/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/charmap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/code copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/code/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/code creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/directionality copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/directionality/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/directionality creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-cool.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-cry.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-embarassed.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-foot-in-mouth.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-frown.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-innocent.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-kiss.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-laughing.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-money-mouth.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-sealed.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-smile.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-surprised.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-tongue-out.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-undecided.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-wink.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-yell.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/example copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example/dialog.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/example copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/example creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/fullpage copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/fullpage/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/fullpage creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/hr copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/hr/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/hr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/image copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/image/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/image creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/imagetools copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/imagetools/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/imagetools creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/importcss copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/importcss/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/importcss creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/layer copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/layer/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/layer creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/link copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/link/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/link creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/lists copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/lists/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/lists creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/media copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/media/moxieplayer.swf -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/media copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/media/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/media creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/noneditable copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/noneditable/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/noneditable creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/paste copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/paste/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/paste creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/preview copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/preview/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/preview creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/print copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/print/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/print creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/save copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/save/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/save creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/table copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/table/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/table creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/template copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/template/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/template creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/textcolor copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/textcolor/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/textcolor creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/textpattern copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/textpattern/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/textpattern creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css/visualblocks.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/visualchars copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/visualchars/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/visualchars creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/plugins/wordcount copying build/lib/mezzanine/core/static/mezzanine/tinymce/plugins/wordcount/plugin.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/plugins/wordcount creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/skins creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/content.inline.min.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/content.min.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/skin.ie7.min.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/skin.min.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.eot -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.svg -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.ttf -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.woff -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.eot -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.svg -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.ttf -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.woff -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/anchor.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/loader.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/object.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img copying build/lib/mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/trans.gif -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/themes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/mezzanine/tinymce/themes/modern copying build/lib/mezzanine/core/static/mezzanine/tinymce/themes/modern/theme.min.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/mezzanine/tinymce/themes/modern creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/static/test copying build/lib/mezzanine/core/static/test/gallery.zip -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/test copying build/lib/mezzanine/core/static/test/image.jpg -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/static/test creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templates copying build/lib/mezzanine/core/templates/base.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates copying build/lib/mezzanine/core/templates/index.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates copying build/lib/mezzanine/core/templates/search_results.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templates/admin copying build/lib/mezzanine/core/templates/admin/base_site.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin copying build/lib/mezzanine/core/templates/admin/index.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin copying build/lib/mezzanine/core/templates/admin/login.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templates/admin/includes copying build/lib/mezzanine/core/templates/admin/includes/app_list.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin/includes copying build/lib/mezzanine/core/templates/admin/includes/content_typed_change_list.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin/includes copying build/lib/mezzanine/core/templates/admin/includes/dropdown_menu.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin/includes copying build/lib/mezzanine/core/templates/admin/includes/recent_actions.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/admin/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templates/email copying build/lib/mezzanine/core/templates/email/base.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/email copying build/lib/mezzanine/core/templates/email/base.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/email creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templates/errors copying build/lib/mezzanine/core/templates/errors/404.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/errors copying build/lib/mezzanine/core/templates/errors/500.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/errors creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/editable_form.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/editable_loader.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/editable_toolbar.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/footer_scripts.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/form_errors.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/form_fields.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/language_selector.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/pagination.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/search_form.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes copying build/lib/mezzanine/core/templates/includes/user_panel.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templates/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/core/templatetags copying build/lib/mezzanine/core/templatetags/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templatetags copying build/lib/mezzanine/core/templatetags/mezzanine_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/core/templatetags creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms copying build/lib/mezzanine/forms/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/fields.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/forms.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/page_processors.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/signals.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms copying build/lib/mezzanine/forms/translation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/fixtures copying build/lib/mezzanine/forms/fixtures/mezzanine_optional.json -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/fixtures creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ar/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ar/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/bg/LC_MESSAGES copying build/lib/mezzanine/forms/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/bg/LC_MESSAGES copying build/lib/mezzanine/forms/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ca/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ca/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/cs/LC_MESSAGES copying build/lib/mezzanine/forms/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/cs/LC_MESSAGES copying build/lib/mezzanine/forms/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/da/LC_MESSAGES copying build/lib/mezzanine/forms/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/da/LC_MESSAGES copying build/lib/mezzanine/forms/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/de/LC_MESSAGES copying build/lib/mezzanine/forms/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/de/LC_MESSAGES copying build/lib/mezzanine/forms/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/en/LC_MESSAGES copying build/lib/mezzanine/forms/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/en/LC_MESSAGES copying build/lib/mezzanine/forms/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/eo/LC_MESSAGES copying build/lib/mezzanine/forms/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/eo/LC_MESSAGES copying build/lib/mezzanine/forms/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/es/LC_MESSAGES copying build/lib/mezzanine/forms/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/es/LC_MESSAGES copying build/lib/mezzanine/forms/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/et/LC_MESSAGES copying build/lib/mezzanine/forms/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/et/LC_MESSAGES copying build/lib/mezzanine/forms/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fa/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fa/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fi/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fi/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/fr/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fr/LC_MESSAGES copying build/lib/mezzanine/forms/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/forms/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/forms/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/hu/LC_MESSAGES copying build/lib/mezzanine/forms/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/hu/LC_MESSAGES copying build/lib/mezzanine/forms/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/forms/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/forms/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/forms/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/forms/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/it/LC_MESSAGES copying build/lib/mezzanine/forms/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/it/LC_MESSAGES copying build/lib/mezzanine/forms/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ja/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ja/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ko/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ko/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/lv/LC_MESSAGES copying build/lib/mezzanine/forms/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/lv/LC_MESSAGES copying build/lib/mezzanine/forms/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/nb/LC_MESSAGES copying build/lib/mezzanine/forms/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/nb/LC_MESSAGES copying build/lib/mezzanine/forms/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/nl/LC_MESSAGES copying build/lib/mezzanine/forms/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/nl/LC_MESSAGES copying build/lib/mezzanine/forms/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pap/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pap/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pl/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pl/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/forms/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/ru/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ru/LC_MESSAGES copying build/lib/mezzanine/forms/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/sk/LC_MESSAGES copying build/lib/mezzanine/forms/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/sk/LC_MESSAGES copying build/lib/mezzanine/forms/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/forms/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/forms/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/sv/LC_MESSAGES copying build/lib/mezzanine/forms/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/sv/LC_MESSAGES copying build/lib/mezzanine/forms/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/tr/LC_MESSAGES copying build/lib/mezzanine/forms/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/tr/LC_MESSAGES copying build/lib/mezzanine/forms/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/forms/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/forms/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/forms/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/forms/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/zh/LC_MESSAGES copying build/lib/mezzanine/forms/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/zh/LC_MESSAGES copying build/lib/mezzanine/forms/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/forms/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/forms/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/forms/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/forms/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/0002_auto_20141227_0224.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/0003_emailfield.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/0004_auto_20150517_0510.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/0005_auto_20151026_1600.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/0006_auto_20170425_2225.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations copying build/lib/mezzanine/forms/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/static creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/static/mezzanine creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/static/mezzanine/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/static/mezzanine/css/admin copying build/lib/mezzanine/forms/static/mezzanine/css/admin/form.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/static/mezzanine/css/admin copying build/lib/mezzanine/forms/static/mezzanine/css/admin/form_entries.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/static/mezzanine/css/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/static/mezzanine/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/static/mezzanine/js/admin copying build/lib/mezzanine/forms/static/mezzanine/js/admin/form_entries.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/static/mezzanine/js/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/templates/admin/forms copying build/lib/mezzanine/forms/templates/admin/forms/change_form.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/admin/forms copying build/lib/mezzanine/forms/templates/admin/forms/entries.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/admin/forms creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/templates/email copying build/lib/mezzanine/forms/templates/email/form_response.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/email copying build/lib/mezzanine/forms/templates/email/form_response.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/email copying build/lib/mezzanine/forms/templates/email/form_response_copies.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/email copying build/lib/mezzanine/forms/templates/email/form_response_copies.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/email creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/forms/templates/pages copying build/lib/mezzanine/forms/templates/pages/form.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/forms/templates/pages creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries copying build/lib/mezzanine/galleries/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries copying build/lib/mezzanine/galleries/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries copying build/lib/mezzanine/galleries/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries copying build/lib/mezzanine/galleries/translation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/fixtures copying build/lib/mezzanine/galleries/fixtures/mezzanine_optional.json -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/fixtures creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ar/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ar/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/bg/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/bg/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ca/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ca/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/cs/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/cs/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/da/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/da/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/de/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/de/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/en/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/en/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/eo/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/eo/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/es/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/es/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/et/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/et/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fa/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fa/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fi/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fi/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/fr/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fr/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/hu/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/hu/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/it/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/it/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ja/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ja/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ko/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ko/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/lv/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/lv/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/nb/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/nb/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/nl/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/nl/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pap/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pap/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pl/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pl/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/ru/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ru/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/sk/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/sk/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/sv/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/sv/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/tr/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/tr/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/zh/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/zh/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/galleries/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/migrations copying build/lib/mezzanine/galleries/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/migrations copying build/lib/mezzanine/galleries/migrations/0002_auto_20141227_0224.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/migrations copying build/lib/mezzanine/galleries/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/static creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/static/mezzanine creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/static/mezzanine/css copying build/lib/mezzanine/galleries/static/mezzanine/css/magnific-popup.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/static/mezzanine/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/static/mezzanine/css/admin copying build/lib/mezzanine/galleries/static/mezzanine/css/admin/gallery.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/static/mezzanine/css/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/static/mezzanine/js copying build/lib/mezzanine/galleries/static/mezzanine/js/magnific-popup.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/static/mezzanine/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/galleries/templates/pages copying build/lib/mezzanine/galleries/templates/pages/gallery.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/galleries/templates/pages creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic copying build/lib/mezzanine/generic/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/fields.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/forms.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/managers.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic copying build/lib/mezzanine/generic/views.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ar/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ar/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/bg/LC_MESSAGES copying build/lib/mezzanine/generic/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/bg/LC_MESSAGES copying build/lib/mezzanine/generic/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ca/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ca/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/cs/LC_MESSAGES copying build/lib/mezzanine/generic/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/cs/LC_MESSAGES copying build/lib/mezzanine/generic/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/da/LC_MESSAGES copying build/lib/mezzanine/generic/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/da/LC_MESSAGES copying build/lib/mezzanine/generic/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/de/LC_MESSAGES copying build/lib/mezzanine/generic/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/de/LC_MESSAGES copying build/lib/mezzanine/generic/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/en/LC_MESSAGES copying build/lib/mezzanine/generic/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/en/LC_MESSAGES copying build/lib/mezzanine/generic/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/eo/LC_MESSAGES copying build/lib/mezzanine/generic/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/eo/LC_MESSAGES copying build/lib/mezzanine/generic/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/es/LC_MESSAGES copying build/lib/mezzanine/generic/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/es/LC_MESSAGES copying build/lib/mezzanine/generic/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/et/LC_MESSAGES copying build/lib/mezzanine/generic/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/et/LC_MESSAGES copying build/lib/mezzanine/generic/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fa/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fa/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fi/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fi/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/fr/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fr/LC_MESSAGES copying build/lib/mezzanine/generic/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/generic/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/generic/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/hu/LC_MESSAGES copying build/lib/mezzanine/generic/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/hu/LC_MESSAGES copying build/lib/mezzanine/generic/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/generic/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/generic/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/generic/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/generic/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/it/LC_MESSAGES copying build/lib/mezzanine/generic/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/it/LC_MESSAGES copying build/lib/mezzanine/generic/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ja/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ja/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ko/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ko/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/lv/LC_MESSAGES copying build/lib/mezzanine/generic/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/lv/LC_MESSAGES copying build/lib/mezzanine/generic/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/nb/LC_MESSAGES copying build/lib/mezzanine/generic/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/nb/LC_MESSAGES copying build/lib/mezzanine/generic/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/nl/LC_MESSAGES copying build/lib/mezzanine/generic/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/nl/LC_MESSAGES copying build/lib/mezzanine/generic/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pap/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pap/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pl/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pl/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/generic/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/ru/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ru/LC_MESSAGES copying build/lib/mezzanine/generic/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/sk/LC_MESSAGES copying build/lib/mezzanine/generic/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/sk/LC_MESSAGES copying build/lib/mezzanine/generic/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/generic/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/generic/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/sv/LC_MESSAGES copying build/lib/mezzanine/generic/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/sv/LC_MESSAGES copying build/lib/mezzanine/generic/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/tr/LC_MESSAGES copying build/lib/mezzanine/generic/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/tr/LC_MESSAGES copying build/lib/mezzanine/generic/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/generic/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/generic/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/generic/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/generic/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/zh/LC_MESSAGES copying build/lib/mezzanine/generic/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/zh/LC_MESSAGES copying build/lib/mezzanine/generic/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/generic/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/generic/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/generic/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/generic/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/migrations copying build/lib/mezzanine/generic/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/migrations copying build/lib/mezzanine/generic/migrations/0002_auto_20141227_0224.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/migrations copying build/lib/mezzanine/generic/migrations/0003_auto_20170411_0504.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/migrations copying build/lib/mezzanine/generic/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templates/admin/includes copying build/lib/mezzanine/generic/templates/admin/includes/recent_comments.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/admin/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templates/email copying build/lib/mezzanine/generic/templates/email/comment_notification.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/email copying build/lib/mezzanine/generic/templates/email/comment_notification.txt -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/email creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templates/generic copying build/lib/mezzanine/generic/templates/generic/comments.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templates/generic/includes copying build/lib/mezzanine/generic/templates/generic/includes/comment.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic/includes copying build/lib/mezzanine/generic/templates/generic/includes/comments.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic/includes copying build/lib/mezzanine/generic/templates/generic/includes/disqus_comments.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic/includes copying build/lib/mezzanine/generic/templates/generic/includes/disqus_counts.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic/includes copying build/lib/mezzanine/generic/templates/generic/includes/disqus_sso.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic/includes copying build/lib/mezzanine/generic/templates/generic/includes/rating.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templates/generic/includes creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/generic/templatetags copying build/lib/mezzanine/generic/templatetags/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templatetags copying build/lib/mezzanine/generic/templatetags/comment_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templatetags copying build/lib/mezzanine/generic/templatetags/disqus_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templatetags copying build/lib/mezzanine/generic/templatetags/keyword_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templatetags copying build/lib/mezzanine/generic/templatetags/rating_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/generic/templatetags creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/mobile copying build/lib/mezzanine/mobile/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/mobile copying build/lib/mezzanine/mobile/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/mobile creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages copying build/lib/mezzanine/pages/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/apps.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/checks.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/context_processors.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/fields.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/managers.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/middleware.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/page_processors.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/translation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages copying build/lib/mezzanine/pages/views.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/fixtures copying build/lib/mezzanine/pages/fixtures/mezzanine_optional.json -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/fixtures copying build/lib/mezzanine/pages/fixtures/mezzanine_required.json -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/fixtures creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ar/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ar/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/bg/LC_MESSAGES copying build/lib/mezzanine/pages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/bg/LC_MESSAGES copying build/lib/mezzanine/pages/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ca/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ca/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/cs/LC_MESSAGES copying build/lib/mezzanine/pages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/cs/LC_MESSAGES copying build/lib/mezzanine/pages/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/da/LC_MESSAGES copying build/lib/mezzanine/pages/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/da/LC_MESSAGES copying build/lib/mezzanine/pages/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/de/LC_MESSAGES copying build/lib/mezzanine/pages/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/de/LC_MESSAGES copying build/lib/mezzanine/pages/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/en/LC_MESSAGES copying build/lib/mezzanine/pages/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/en/LC_MESSAGES copying build/lib/mezzanine/pages/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/eo/LC_MESSAGES copying build/lib/mezzanine/pages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/eo/LC_MESSAGES copying build/lib/mezzanine/pages/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/es/LC_MESSAGES copying build/lib/mezzanine/pages/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/es/LC_MESSAGES copying build/lib/mezzanine/pages/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/et/LC_MESSAGES copying build/lib/mezzanine/pages/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/et/LC_MESSAGES copying build/lib/mezzanine/pages/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fa/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fa/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fi/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fi/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/fr/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fr/LC_MESSAGES copying build/lib/mezzanine/pages/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/pages/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/pages/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/hu/LC_MESSAGES copying build/lib/mezzanine/pages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/hu/LC_MESSAGES copying build/lib/mezzanine/pages/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/pages/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/pages/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/pages/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/pages/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/it/LC_MESSAGES copying build/lib/mezzanine/pages/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/it/LC_MESSAGES copying build/lib/mezzanine/pages/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ja/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ja/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ko/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ko/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/lv/LC_MESSAGES copying build/lib/mezzanine/pages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/lv/LC_MESSAGES copying build/lib/mezzanine/pages/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/nb/LC_MESSAGES copying build/lib/mezzanine/pages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/nb/LC_MESSAGES copying build/lib/mezzanine/pages/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/nl/LC_MESSAGES copying build/lib/mezzanine/pages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/nl/LC_MESSAGES copying build/lib/mezzanine/pages/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pap/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pap/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pl/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pl/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/pages/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/ru/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ru/LC_MESSAGES copying build/lib/mezzanine/pages/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/sk/LC_MESSAGES copying build/lib/mezzanine/pages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/sk/LC_MESSAGES copying build/lib/mezzanine/pages/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/pages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/pages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/sv/LC_MESSAGES copying build/lib/mezzanine/pages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/sv/LC_MESSAGES copying build/lib/mezzanine/pages/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/tr/LC_MESSAGES copying build/lib/mezzanine/pages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/tr/LC_MESSAGES copying build/lib/mezzanine/pages/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/pages/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/pages/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/pages/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/pages/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/zh/LC_MESSAGES copying build/lib/mezzanine/pages/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/zh/LC_MESSAGES copying build/lib/mezzanine/pages/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/pages/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/pages/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/pages/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/pages/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/migrations copying build/lib/mezzanine/pages/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/migrations copying build/lib/mezzanine/pages/migrations/0002_auto_20141227_0224.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/migrations copying build/lib/mezzanine/pages/migrations/0003_auto_20150527_1555.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/migrations copying build/lib/mezzanine/pages/migrations/0004_auto_20170411_0504.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/migrations copying build/lib/mezzanine/pages/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/static creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/static/mezzanine creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/static/mezzanine/css creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/static/mezzanine/css/admin copying build/lib/mezzanine/pages/static/mezzanine/css/admin/page_tree.css -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/static/mezzanine/css/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/static/mezzanine/js creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/static/mezzanine/js/admin copying build/lib/mezzanine/pages/static/mezzanine/js/admin/jquery.mjs.nestedSortable.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/static/mezzanine/js/admin copying build/lib/mezzanine/pages/static/mezzanine/js/admin/page_tree.js -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/static/mezzanine/js/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates/admin creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates/admin/pages creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates/admin/pages/link copying build/lib/mezzanine/pages/templates/admin/pages/link/change_form.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/admin/pages/link creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates/admin/pages/page copying build/lib/mezzanine/pages/templates/admin/pages/page/change_list.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/admin/pages/page copying build/lib/mezzanine/pages/templates/admin/pages/page/delete_confirmation.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/admin/pages/page creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates/pages copying build/lib/mezzanine/pages/templates/pages/index.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages copying build/lib/mezzanine/pages/templates/pages/page.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages copying build/lib/mezzanine/pages/templates/pages/richtextpage.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/admin.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/breadcrumb.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/dropdown.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/footer.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/footer_tree.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/mobile.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/primary.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus copying build/lib/mezzanine/pages/templates/pages/menus/tree.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templates/pages/menus creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/pages/templatetags copying build/lib/mezzanine/pages/templatetags/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templatetags copying build/lib/mezzanine/pages/templatetags/pages_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/pages/templatetags creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/project_template copying build/lib/mezzanine/project_template/.gitignore -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template copying build/lib/mezzanine/project_template/.hgignore -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template copying build/lib/mezzanine/project_template/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template copying build/lib/mezzanine/project_template/manage.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/project_template/project_name copying build/lib/mezzanine/project_template/project_name/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template/project_name copying build/lib/mezzanine/project_template/project_name/local_settings.py.template -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template/project_name copying build/lib/mezzanine/project_template/project_name/settings.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template/project_name copying build/lib/mezzanine/project_template/project_name/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template/project_name copying build/lib/mezzanine/project_template/project_name/wsgi.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/project_template/project_name creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/template copying build/lib/mezzanine/template/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/template copying build/lib/mezzanine/template/loader_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/template creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/template/loaders copying build/lib/mezzanine/template/loaders/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/template/loaders copying build/lib/mezzanine/template/loaders/host_themes.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/template/loaders creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter copying build/lib/mezzanine/twitter/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter copying build/lib/mezzanine/twitter/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter copying build/lib/mezzanine/twitter/apps.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter copying build/lib/mezzanine/twitter/checks.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter copying build/lib/mezzanine/twitter/defaults.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter copying build/lib/mezzanine/twitter/managers.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter copying build/lib/mezzanine/twitter/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ar creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ar/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ar/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ar/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ar/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ar/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/bg creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/bg/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/bg/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/bg/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/bg/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/bg/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ca creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ca/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ca/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ca/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ca/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ca/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/cs creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/cs/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/cs/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/cs/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/cs/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/cs/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/da creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/da/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/da/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/da/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/da/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/da/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/de creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/de/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/de/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/de/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/de/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/de/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/en creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/en/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/en/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/en/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/en/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/en/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/eo creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/eo/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/eo/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/eo/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/eo/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/eo/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/es creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/es/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/es/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/es/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/es/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/es/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/et creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/et/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/et/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/et/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/et/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/et/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fa creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fa/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fa/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fa/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fa/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fa/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fa_IR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fa_IR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fa_IR/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fa_IR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fa_IR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fi creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fi/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fi/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fi/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fi/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fi/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/fr/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fr/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/fr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/fr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/hr_HR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/hr_HR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/hr_HR/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/hr_HR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/hr_HR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/hu creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/hu/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/hu/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/hu/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/hu/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/hu/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/id_ID creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/id_ID/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/id_ID/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/id_ID/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/id_ID/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/is_IS creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/is_IS/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/is_IS/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/is_IS/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/is_IS/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/it creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/it/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/it/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/it/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/it/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/it/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ja creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ja/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ja/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ja/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ja/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ja/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ko creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ko/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ko/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ko/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ko/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ko/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/lv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/lv/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/lv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/lv/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/lv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/lv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/nb creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/nb/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/nb/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/nb/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/nb/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/nb/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/nl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/nl/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/nl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/nl/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/nl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/nl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pap creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pap/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pap/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pap/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pap/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pap/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pl creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pl/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pl/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pl/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pl/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pl/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pt_BR creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pt_BR/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pt_BR/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pt_PT creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pt_PT/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pt_PT/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/pt_PT/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/pt_PT/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ru creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/ru/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ru/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ru/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/ru/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/ru/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/sk creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/sk/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/sk/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/sk/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/sk/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/sk/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/sr_Latn creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/sr_Latn/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/sr_Latn/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/sv creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/sv/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/sv/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/sv/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/sv/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/sv/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/tr creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/tr/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/tr/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/tr/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/tr/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/tr/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/uk_UA creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/uk_UA/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/uk_UA/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/uk_UA/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/uk_UA/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/vi_VN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/vi_VN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/vi_VN/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/vi_VN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/vi_VN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/zh creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/zh/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/zh/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/zh/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/zh/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/zh/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/zh_CN creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/zh_CN/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/zh_CN/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/zh_CN/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/zh_TW creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/zh_TW/LC_MESSAGES/django.mo -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/zh_TW/LC_MESSAGES copying build/lib/mezzanine/twitter/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/locale/zh_TW/LC_MESSAGES creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/management copying build/lib/mezzanine/twitter/management/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/management creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/management/commands copying build/lib/mezzanine/twitter/management/commands/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/management/commands copying build/lib/mezzanine/twitter/management/commands/poll_twitter.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/management/commands creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/migrations copying build/lib/mezzanine/twitter/migrations/0001_initial.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/migrations copying build/lib/mezzanine/twitter/migrations/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/migrations creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/templates creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/templates/twitter copying build/lib/mezzanine/twitter/templates/twitter/tweets.html -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/templates/twitter creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/twitter/templatetags copying build/lib/mezzanine/twitter/templatetags/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/templatetags copying build/lib/mezzanine/twitter/templatetags/twitter_tags.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/twitter/templatetags creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine/utils copying build/lib/mezzanine/utils/__init__.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/admin.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/cache.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/conf.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/deprecation.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/docs.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/email.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/html.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/importing.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/models.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/sites.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/static.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/tests.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/timezone.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/urls.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils copying build/lib/mezzanine/utils/views.py -> build/bdist.netbsd-9.0-amd64/wheel/./mezzanine/utils running install_egg_info Copying Mezzanine.egg-info to build/bdist.netbsd-9.0-amd64/wheel/./Mezzanine-6.0.0-py3.12.egg-info running install_scripts creating build/bdist.netbsd-9.0-amd64/wheel/mezzanine-6.0.0.dist-info/WHEEL creating '/pbulk/work/www/py-mezzanine/work/Mezzanine-6.0.0/dist/.tmp-9cplbnna/mezzanine-6.0.0-py2.py3-none-any.whl' and adding 'build/bdist.netbsd-9.0-amd64/wheel' to it adding 'mezzanine/__init__.py' adding 'mezzanine/urls.py' adding 'mezzanine/accounts/__init__.py' adding 'mezzanine/accounts/admin.py' adding 'mezzanine/accounts/defaults.py' adding 'mezzanine/accounts/forms.py' adding 'mezzanine/accounts/models.py' adding 'mezzanine/accounts/urls.py' adding 'mezzanine/accounts/views.py' adding 'mezzanine/accounts/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/accounts/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/accounts/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/accounts/templates/accounts/account_form.html' adding 'mezzanine/accounts/templates/accounts/account_login.html' adding 'mezzanine/accounts/templates/accounts/account_password_reset.html' adding 'mezzanine/accounts/templates/accounts/account_profile.html' adding 'mezzanine/accounts/templates/accounts/account_profile_update.html' adding 'mezzanine/accounts/templates/accounts/account_signup.html' adding 'mezzanine/accounts/templates/accounts/includes/user_panel.html' adding 'mezzanine/accounts/templates/accounts/includes/user_panel_nav.html' adding 'mezzanine/accounts/templates/admin/profile_inline.html' adding 'mezzanine/accounts/templates/email/account_approve.html' adding 'mezzanine/accounts/templates/email/account_approve.txt' adding 'mezzanine/accounts/templates/email/account_approve_subject.txt' adding 'mezzanine/accounts/templates/email/account_approved.html' adding 'mezzanine/accounts/templates/email/account_approved.txt' adding 'mezzanine/accounts/templates/email/account_approved_subject.txt' adding 'mezzanine/accounts/templates/email/password_reset_verify.html' adding 'mezzanine/accounts/templates/email/password_reset_verify.txt' adding 'mezzanine/accounts/templates/email/password_reset_verify_subject.txt' adding 'mezzanine/accounts/templates/email/signup_verify.html' adding 'mezzanine/accounts/templates/email/signup_verify.txt' adding 'mezzanine/accounts/templates/email/signup_verify_subject.txt' adding 'mezzanine/accounts/templatetags/__init__.py' adding 'mezzanine/accounts/templatetags/accounts_tags.py' adding 'mezzanine/bin/__init__.py' adding 'mezzanine/bin/mezzanine_project.py' adding 'mezzanine/bin/management/__init__.py' adding 'mezzanine/bin/management/commands/__init__.py' adding 'mezzanine/bin/management/commands/mezzanine_project.py' adding 'mezzanine/blog/__init__.py' adding 'mezzanine/blog/admin.py' adding 'mezzanine/blog/defaults.py' adding 'mezzanine/blog/feeds.py' adding 'mezzanine/blog/forms.py' adding 'mezzanine/blog/models.py' adding 'mezzanine/blog/translation.py' adding 'mezzanine/blog/urls.py' adding 'mezzanine/blog/views.py' adding 'mezzanine/blog/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/blog/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/blog/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/blog/management/__init__.py' adding 'mezzanine/blog/management/base.py' adding 'mezzanine/blog/management/commands/__init__.py' adding 'mezzanine/blog/management/commands/import_blogger.py' adding 'mezzanine/blog/management/commands/import_blogml.py' adding 'mezzanine/blog/management/commands/import_posterous.py' adding 'mezzanine/blog/management/commands/import_rss.py' adding 'mezzanine/blog/management/commands/import_tumblr.py' adding 'mezzanine/blog/management/commands/import_wordpress.py' adding 'mezzanine/blog/migrations/0001_initial.py' adding 'mezzanine/blog/migrations/0002_auto_20150527_1555.py' adding 'mezzanine/blog/migrations/0003_auto_20170411_0504.py' adding 'mezzanine/blog/migrations/__init__.py' adding 'mezzanine/blog/templates/admin/includes/quick_blog.html' adding 'mezzanine/blog/templates/blog/blog_post_detail.html' adding 'mezzanine/blog/templates/blog/blog_post_list.html' adding 'mezzanine/blog/templates/blog/includes/filter_panel.html' adding 'mezzanine/blog/templatetags/__init__.py' adding 'mezzanine/blog/templatetags/blog_tags.py' adding 'mezzanine/boot/__init__.py' adding 'mezzanine/boot/lazy_admin.py' adding 'mezzanine/boot/models.py' adding 'mezzanine/conf/__init__.py' adding 'mezzanine/conf/admin.py' adding 'mezzanine/conf/context_processors.py' adding 'mezzanine/conf/forms.py' adding 'mezzanine/conf/models.py' adding 'mezzanine/conf/translation.py' adding 'mezzanine/conf/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/conf/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/conf/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/conf/migrations/0001_initial.py' adding 'mezzanine/conf/migrations/__init__.py' adding 'mezzanine/conf/static/mezzanine/css/admin/settings.css' adding 'mezzanine/conf/static/mezzanine/js/admin/tabbed_translatable_settings.js' adding 'mezzanine/conf/templates/admin/conf/setting/change_list.html' adding 'mezzanine/core/__init__.py' adding 'mezzanine/core/admin.py' adding 'mezzanine/core/apps.py' adding 'mezzanine/core/auth_backends.py' adding 'mezzanine/core/checks.py' adding 'mezzanine/core/defaults.py' adding 'mezzanine/core/exceptions.py' adding 'mezzanine/core/fields.py' adding 'mezzanine/core/forms.py' adding 'mezzanine/core/managers.py' adding 'mezzanine/core/middleware.py' adding 'mezzanine/core/models.py' adding 'mezzanine/core/request.py' adding 'mezzanine/core/sitemaps.py' adding 'mezzanine/core/translation.py' adding 'mezzanine/core/urls.py' adding 'mezzanine/core/views.py' adding 'mezzanine/core/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/core/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/core/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/core/management/__init__.py' adding 'mezzanine/core/management/commands/__init__.py' adding 'mezzanine/core/management/commands/collecttemplates.py' adding 'mezzanine/core/management/commands/createdb.py' adding 'mezzanine/core/management/commands/runserver.py' adding 'mezzanine/core/migrations/0001_initial.py' adding 'mezzanine/core/migrations/0002_auto_20150414_2140.py' adding 'mezzanine/core/migrations/__init__.py' adding 'mezzanine/core/static/robots.txt' adding 'mezzanine/core/static/admin/img/admin/README' adding 'mezzanine/core/static/admin/img/admin/arrow-down.gif' adding 'mezzanine/core/static/admin/img/admin/arrow-up.gif' adding 'mezzanine/core/static/admin/img/admin/icon_deletelink.gif' adding 'mezzanine/core/static/admin/js/collapse.js' adding 'mezzanine/core/static/css/bootstrap-rtl.css' adding 'mezzanine/core/static/css/bootstrap-theme.css' adding 'mezzanine/core/static/css/bootstrap.css' adding 'mezzanine/core/static/css/mezzanine.css' adding 'mezzanine/core/static/fonts/glyphicons-halflings-regular.eot' adding 'mezzanine/core/static/fonts/glyphicons-halflings-regular.svg' adding 'mezzanine/core/static/fonts/glyphicons-halflings-regular.ttf' adding 'mezzanine/core/static/fonts/glyphicons-halflings-regular.woff' adding 'mezzanine/core/static/img/favicon.ico' adding 'mezzanine/core/static/js/bootstrap-extras.js' adding 'mezzanine/core/static/js/bootstrap.js' adding 'mezzanine/core/static/js/html5shiv.js' adding 'mezzanine/core/static/js/respond.min.js' adding 'mezzanine/core/static/mezzanine/chosen/chosen-0.9.12.jquery.js' adding 'mezzanine/core/static/mezzanine/chosen/chosen-sprite-dark.png' adding 'mezzanine/core/static/mezzanine/chosen/chosen-sprite.png' adding 'mezzanine/core/static/mezzanine/chosen/chosen.css' adding 'mezzanine/core/static/mezzanine/css/editable.css' adding 'mezzanine/core/static/mezzanine/css/tinymce.css' adding 'mezzanine/core/static/mezzanine/css/admin/dashboard.css' adding 'mezzanine/core/static/mezzanine/css/admin/global.css' adding 'mezzanine/core/static/mezzanine/css/admin/rtl.css' adding 'mezzanine/core/static/mezzanine/css/admin/tabbed_translation_fields.css' adding 'mezzanine/core/static/mezzanine/css/smoothness/jquery-ui.css' adding 'mezzanine/core/static/mezzanine/css/smoothness/jquery-ui.min.css' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_flat_75_ffffff_40x100.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_65_ffffff_1x400.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_75_dadada_1x400.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_222222_256x240.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_2e83ff_256x240.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_454545_256x240.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_888888_256x240.png' adding 'mezzanine/core/static/mezzanine/css/smoothness/images/ui-icons_cd0a0a_256x240.png' adding 'mezzanine/core/static/mezzanine/img/loadingAnimation.gif' adding 'mezzanine/core/static/mezzanine/js/editable.js' adding 'mezzanine/core/static/mezzanine/js/jquery-3.4.1.js' adding 'mezzanine/core/static/mezzanine/js/jquery-ui-1.12.1.js' adding 'mezzanine/core/static/mezzanine/js/jquery.form.js' adding 'mezzanine/core/static/mezzanine/js/jquery.tools.overlay.js' adding 'mezzanine/core/static/mezzanine/js/jquery.tools.toolbox.expose.js' adding 'mezzanine/core/static/mezzanine/js/tinymce_setup.js' adding 'mezzanine/core/static/mezzanine/js/admin/ajax_csrf.js' adding 'mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js' adding 'mezzanine/core/static/mezzanine/js/admin/keywords_field.js' adding 'mezzanine/core/static/mezzanine/js/admin/login.js' adding 'mezzanine/core/static/mezzanine/js/admin/navigation.js' adding 'mezzanine/core/static/mezzanine/js/admin/tabbed_translation_fields.js' adding 'mezzanine/core/static/mezzanine/tinymce/jquery.tinymce.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/license.txt' adding 'mezzanine/core/static/mezzanine/tinymce/tinymce.css' adding 'mezzanine/core/static/mezzanine/tinymce/tinymce.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/ar.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/ca.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/cs.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/da.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/de.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/es.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/et.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/fa.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/fa_IR.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/fi.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/fr_FR.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/hr.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/hu_HU.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/id.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/is_IS.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/it.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/ja.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/ko_KR.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/lv.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/nb_NO.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/nl.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/pl.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/pt_BR.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/pt_PT.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/ru.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/sk.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/sr.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/sv_SE.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/tr.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/uk_UA.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/vi.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/zh_CN.js' adding 'mezzanine/core/static/mezzanine/tinymce/langs/zh_TW.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/advlist/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/anchor/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/autolink/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/autoresize/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/autosave/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/bbcode/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/charmap/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/code/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/colorpicker/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/contextmenu/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/directionality/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-cool.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-cry.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-embarassed.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-foot-in-mouth.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-frown.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-innocent.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-kiss.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-laughing.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-money-mouth.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-sealed.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-smile.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-surprised.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-tongue-out.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-undecided.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-wink.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/emoticons/img/smiley-yell.gif' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/example/dialog.html' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/example/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/example_dependency/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/fullpage/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/fullscreen/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/hr/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/image/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/imagetools/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/importcss/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/insertdatetime/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/layer/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/legacyoutput/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/link/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/lists/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/media/moxieplayer.swf' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/media/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/nonbreaking/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/noneditable/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/pagebreak/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/paste/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/preview/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/print/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/save/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/searchreplace/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/spellchecker/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/tabfocus/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/table/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/template/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/textcolor/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/textpattern/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/visualblocks/css/visualblocks.css' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/visualchars/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/plugins/wordcount/plugin.min.js' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/content.inline.min.css' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/content.min.css' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/skin.ie7.min.css' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/skin.min.css' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.eot' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.svg' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.ttf' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce-small.woff' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.eot' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.svg' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.ttf' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/fonts/tinymce.woff' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/anchor.gif' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/loader.gif' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/object.gif' adding 'mezzanine/core/static/mezzanine/tinymce/skins/lightgray/img/trans.gif' adding 'mezzanine/core/static/mezzanine/tinymce/themes/modern/theme.min.js' adding 'mezzanine/core/static/test/gallery.zip' adding 'mezzanine/core/static/test/image.jpg' adding 'mezzanine/core/templates/base.html' adding 'mezzanine/core/templates/index.html' adding 'mezzanine/core/templates/search_results.html' adding 'mezzanine/core/templates/admin/base_site.html' adding 'mezzanine/core/templates/admin/index.html' adding 'mezzanine/core/templates/admin/login.html' adding 'mezzanine/core/templates/admin/includes/app_list.html' adding 'mezzanine/core/templates/admin/includes/content_typed_change_list.html' adding 'mezzanine/core/templates/admin/includes/dropdown_menu.html' adding 'mezzanine/core/templates/admin/includes/recent_actions.html' adding 'mezzanine/core/templates/email/base.html' adding 'mezzanine/core/templates/email/base.txt' adding 'mezzanine/core/templates/errors/404.html' adding 'mezzanine/core/templates/errors/500.html' adding 'mezzanine/core/templates/includes/editable_form.html' adding 'mezzanine/core/templates/includes/editable_loader.html' adding 'mezzanine/core/templates/includes/editable_toolbar.html' adding 'mezzanine/core/templates/includes/footer_scripts.html' adding 'mezzanine/core/templates/includes/form_errors.html' adding 'mezzanine/core/templates/includes/form_fields.html' adding 'mezzanine/core/templates/includes/language_selector.html' adding 'mezzanine/core/templates/includes/pagination.html' adding 'mezzanine/core/templates/includes/search_form.html' adding 'mezzanine/core/templates/includes/user_panel.html' adding 'mezzanine/core/templatetags/__init__.py' adding 'mezzanine/core/templatetags/mezzanine_tags.py' adding 'mezzanine/forms/__init__.py' adding 'mezzanine/forms/admin.py' adding 'mezzanine/forms/defaults.py' adding 'mezzanine/forms/fields.py' adding 'mezzanine/forms/forms.py' adding 'mezzanine/forms/models.py' adding 'mezzanine/forms/page_processors.py' adding 'mezzanine/forms/signals.py' adding 'mezzanine/forms/translation.py' adding 'mezzanine/forms/fixtures/mezzanine_optional.json' adding 'mezzanine/forms/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/forms/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/forms/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/forms/migrations/0001_initial.py' adding 'mezzanine/forms/migrations/0002_auto_20141227_0224.py' adding 'mezzanine/forms/migrations/0003_emailfield.py' adding 'mezzanine/forms/migrations/0004_auto_20150517_0510.py' adding 'mezzanine/forms/migrations/0005_auto_20151026_1600.py' adding 'mezzanine/forms/migrations/0006_auto_20170425_2225.py' adding 'mezzanine/forms/migrations/__init__.py' adding 'mezzanine/forms/static/mezzanine/css/admin/form.css' adding 'mezzanine/forms/static/mezzanine/css/admin/form_entries.css' adding 'mezzanine/forms/static/mezzanine/js/admin/form_entries.js' adding 'mezzanine/forms/templates/admin/forms/change_form.html' adding 'mezzanine/forms/templates/admin/forms/entries.html' adding 'mezzanine/forms/templates/email/form_response.html' adding 'mezzanine/forms/templates/email/form_response.txt' adding 'mezzanine/forms/templates/email/form_response_copies.html' adding 'mezzanine/forms/templates/email/form_response_copies.txt' adding 'mezzanine/forms/templates/pages/form.html' adding 'mezzanine/galleries/__init__.py' adding 'mezzanine/galleries/admin.py' adding 'mezzanine/galleries/models.py' adding 'mezzanine/galleries/translation.py' adding 'mezzanine/galleries/fixtures/mezzanine_optional.json' adding 'mezzanine/galleries/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/galleries/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/galleries/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/galleries/migrations/0001_initial.py' adding 'mezzanine/galleries/migrations/0002_auto_20141227_0224.py' adding 'mezzanine/galleries/migrations/__init__.py' adding 'mezzanine/galleries/static/mezzanine/css/magnific-popup.css' adding 'mezzanine/galleries/static/mezzanine/css/admin/gallery.css' adding 'mezzanine/galleries/static/mezzanine/js/magnific-popup.js' adding 'mezzanine/galleries/templates/pages/gallery.html' adding 'mezzanine/generic/__init__.py' adding 'mezzanine/generic/admin.py' adding 'mezzanine/generic/defaults.py' adding 'mezzanine/generic/fields.py' adding 'mezzanine/generic/forms.py' adding 'mezzanine/generic/managers.py' adding 'mezzanine/generic/models.py' adding 'mezzanine/generic/urls.py' adding 'mezzanine/generic/views.py' adding 'mezzanine/generic/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/generic/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/generic/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/generic/migrations/0001_initial.py' adding 'mezzanine/generic/migrations/0002_auto_20141227_0224.py' adding 'mezzanine/generic/migrations/0003_auto_20170411_0504.py' adding 'mezzanine/generic/migrations/__init__.py' adding 'mezzanine/generic/templates/admin/includes/recent_comments.html' adding 'mezzanine/generic/templates/email/comment_notification.html' adding 'mezzanine/generic/templates/email/comment_notification.txt' adding 'mezzanine/generic/templates/generic/comments.html' adding 'mezzanine/generic/templates/generic/includes/comment.html' adding 'mezzanine/generic/templates/generic/includes/comments.html' adding 'mezzanine/generic/templates/generic/includes/disqus_comments.html' adding 'mezzanine/generic/templates/generic/includes/disqus_counts.html' adding 'mezzanine/generic/templates/generic/includes/disqus_sso.html' adding 'mezzanine/generic/templates/generic/includes/rating.html' adding 'mezzanine/generic/templatetags/__init__.py' adding 'mezzanine/generic/templatetags/comment_tags.py' adding 'mezzanine/generic/templatetags/disqus_tags.py' adding 'mezzanine/generic/templatetags/keyword_tags.py' adding 'mezzanine/generic/templatetags/rating_tags.py' adding 'mezzanine/mobile/__init__.py' adding 'mezzanine/mobile/models.py' adding 'mezzanine/pages/__init__.py' adding 'mezzanine/pages/admin.py' adding 'mezzanine/pages/apps.py' adding 'mezzanine/pages/checks.py' adding 'mezzanine/pages/context_processors.py' adding 'mezzanine/pages/defaults.py' adding 'mezzanine/pages/fields.py' adding 'mezzanine/pages/managers.py' adding 'mezzanine/pages/middleware.py' adding 'mezzanine/pages/models.py' adding 'mezzanine/pages/page_processors.py' adding 'mezzanine/pages/translation.py' adding 'mezzanine/pages/urls.py' adding 'mezzanine/pages/views.py' adding 'mezzanine/pages/fixtures/mezzanine_optional.json' adding 'mezzanine/pages/fixtures/mezzanine_required.json' adding 'mezzanine/pages/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/pages/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/pages/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/pages/migrations/0001_initial.py' adding 'mezzanine/pages/migrations/0002_auto_20141227_0224.py' adding 'mezzanine/pages/migrations/0003_auto_20150527_1555.py' adding 'mezzanine/pages/migrations/0004_auto_20170411_0504.py' adding 'mezzanine/pages/migrations/__init__.py' adding 'mezzanine/pages/static/mezzanine/css/admin/page_tree.css' adding 'mezzanine/pages/static/mezzanine/js/admin/jquery.mjs.nestedSortable.js' adding 'mezzanine/pages/static/mezzanine/js/admin/page_tree.js' adding 'mezzanine/pages/templates/admin/pages/link/change_form.html' adding 'mezzanine/pages/templates/admin/pages/page/change_list.html' adding 'mezzanine/pages/templates/admin/pages/page/delete_confirmation.html' adding 'mezzanine/pages/templates/pages/index.html' adding 'mezzanine/pages/templates/pages/page.html' adding 'mezzanine/pages/templates/pages/richtextpage.html' adding 'mezzanine/pages/templates/pages/menus/admin.html' adding 'mezzanine/pages/templates/pages/menus/breadcrumb.html' adding 'mezzanine/pages/templates/pages/menus/dropdown.html' adding 'mezzanine/pages/templates/pages/menus/footer.html' adding 'mezzanine/pages/templates/pages/menus/footer_tree.html' adding 'mezzanine/pages/templates/pages/menus/mobile.html' adding 'mezzanine/pages/templates/pages/menus/primary.html' adding 'mezzanine/pages/templates/pages/menus/tree.html' adding 'mezzanine/pages/templatetags/__init__.py' adding 'mezzanine/pages/templatetags/pages_tags.py' adding 'mezzanine/project_template/.gitignore' adding 'mezzanine/project_template/.hgignore' adding 'mezzanine/project_template/__init__.py' adding 'mezzanine/project_template/manage.py' adding 'mezzanine/project_template/project_name/__init__.py' adding 'mezzanine/project_template/project_name/local_settings.py.template' adding 'mezzanine/project_template/project_name/settings.py' adding 'mezzanine/project_template/project_name/urls.py' adding 'mezzanine/project_template/project_name/wsgi.py' adding 'mezzanine/template/__init__.py' adding 'mezzanine/template/loader_tags.py' adding 'mezzanine/template/loaders/__init__.py' adding 'mezzanine/template/loaders/host_themes.py' adding 'mezzanine/twitter/__init__.py' adding 'mezzanine/twitter/admin.py' adding 'mezzanine/twitter/apps.py' adding 'mezzanine/twitter/checks.py' adding 'mezzanine/twitter/defaults.py' adding 'mezzanine/twitter/managers.py' adding 'mezzanine/twitter/models.py' adding 'mezzanine/twitter/locale/ar/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/ar/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/bg/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/bg/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/ca/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/ca/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/cs/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/cs/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/da/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/da/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/de/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/de/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/en/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/en/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/eo/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/eo/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/es/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/es/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/et/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/et/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/fa/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/fa/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/fa_IR/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/fa_IR/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/fi/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/fi/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/fr/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/fr/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/hr_HR/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/hr_HR/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/hu/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/hu/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/id_ID/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/id_ID/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/is_IS/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/is_IS/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/it/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/it/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/ja/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/ja/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/ko/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/ko/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/lv/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/lv/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/nb/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/nb/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/nl/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/nl/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/pap/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/pap/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/pl/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/pl/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/pt_BR/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/pt_BR/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/pt_PT/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/pt_PT/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/ru/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/ru/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/sk/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/sk/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/sr_Latn/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/sv/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/sv/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/tr/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/tr/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/uk_UA/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/uk_UA/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/vi_VN/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/vi_VN/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/zh/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/zh/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/zh_CN/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/zh_CN/LC_MESSAGES/django.po' adding 'mezzanine/twitter/locale/zh_TW/LC_MESSAGES/django.mo' adding 'mezzanine/twitter/locale/zh_TW/LC_MESSAGES/django.po' adding 'mezzanine/twitter/management/__init__.py' adding 'mezzanine/twitter/management/commands/__init__.py' adding 'mezzanine/twitter/management/commands/poll_twitter.py' adding 'mezzanine/twitter/migrations/0001_initial.py' adding 'mezzanine/twitter/migrations/__init__.py' adding 'mezzanine/twitter/templates/twitter/tweets.html' adding 'mezzanine/twitter/templatetags/__init__.py' adding 'mezzanine/twitter/templatetags/twitter_tags.py' adding 'mezzanine/utils/__init__.py' adding 'mezzanine/utils/admin.py' adding 'mezzanine/utils/cache.py' adding 'mezzanine/utils/conf.py' adding 'mezzanine/utils/deprecation.py' adding 'mezzanine/utils/docs.py' adding 'mezzanine/utils/email.py' adding 'mezzanine/utils/html.py' adding 'mezzanine/utils/importing.py' adding 'mezzanine/utils/models.py' adding 'mezzanine/utils/sites.py' adding 'mezzanine/utils/static.py' adding 'mezzanine/utils/tests.py' adding 'mezzanine/utils/timezone.py' adding 'mezzanine/utils/urls.py' adding 'mezzanine/utils/views.py' adding 'mezzanine-6.0.0.dist-info/LICENSE' adding 'mezzanine-6.0.0.dist-info/METADATA' adding 'mezzanine-6.0.0.dist-info/WHEEL' adding 'mezzanine-6.0.0.dist-info/entry_points.txt' adding 'mezzanine-6.0.0.dist-info/top_level.txt' adding 'mezzanine-6.0.0.dist-info/RECORD' removing build/bdist.netbsd-9.0-amd64/wheel Successfully built mezzanine-6.0.0-py2.py3-none-any.whl