>>> py3-django-registration: Building community/py3-django-registration 3.3-r2 (using abuild 3.11.0_rc13-r0) started Sun, 23 Apr 2023 01:37:06 +0000 >>> py3-django-registration: Checking sanity of /home/buildozer/aports/community/py3-django-registration/APKBUILD... >>> py3-django-registration: Analyzing dependencies... >>> py3-django-registration: Installing for build: build-base python3 py3-setuptools (1/19) Installing libbz2 (1.0.8-r5) (2/19) Installing libffi (3.4.4-r2) (3/19) Installing gdbm (1.23-r1) (4/19) Installing xz-libs (5.4.2-r1) (5/19) Installing mpdecimal (2.5.1-r2) (6/19) Installing libpanelw (6.4_p20230401-r5) (7/19) Installing readline (8.2.1-r1) (8/19) Installing sqlite-libs (3.41.2-r2) (9/19) Installing python3 (3.11.3-r10) (10/19) Installing python3-pycache-pyc0 (3.11.3-r10) (11/19) Installing pyc (0.1-r0) (12/19) Installing python3-pyc (3.11.3-r10) (13/19) Installing py3-parsing (3.0.9-r2) (14/19) Installing py3-parsing-pyc (3.0.9-r2) (15/19) Installing py3-packaging (23.1-r1) (16/19) Installing py3-packaging-pyc (23.1-r1) (17/19) Installing py3-setuptools (67.7.1-r0) (18/19) Installing py3-setuptools-pyc (67.7.1-r0) (19/19) Installing .makedepends-py3-django-registration (20230423.013707) Executing busybox-1.36.0-r7.trigger OK: 329 MiB in 117 packages >>> py3-django-registration: Cleaning up srcdir >>> py3-django-registration: Cleaning up pkgdir >>> py3-django-registration: Fetching https://distfiles.alpinelinux.org/distfiles/v3.18/django-registration-3.3.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 146 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 >>> py3-django-registration: Fetching django-registration-3.3.tar.gz::https://github.com/ubernostrum/django-registration/archive/3.3.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 77483 0 77483 0 0 91356 0 --:--:-- --:--:-- --:--:-- 1036k >>> py3-django-registration: Fetching https://distfiles.alpinelinux.org/distfiles/v3.18/django-registration-3.3.tar.gz >>> py3-django-registration: Checking sha512sums... django-registration-3.3.tar.gz: OK >>> py3-django-registration: Unpacking /var/cache/distfiles/v3.18/django-registration-3.3.tar.gz... /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running build running build_py creating build creating build/lib creating build/lib/django_registration copying src/django_registration/__init__.py -> build/lib/django_registration copying src/django_registration/signals.py -> build/lib/django_registration copying src/django_registration/views.py -> build/lib/django_registration copying src/django_registration/forms.py -> build/lib/django_registration copying src/django_registration/validators.py -> build/lib/django_registration copying src/django_registration/exceptions.py -> build/lib/django_registration creating build/lib/django_registration/migrations copying src/django_registration/migrations/__init__.py -> build/lib/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> build/lib/django_registration/migrations creating build/lib/django_registration/backends copying src/django_registration/backends/__init__.py -> build/lib/django_registration/backends creating build/lib/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> build/lib/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> build/lib/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> build/lib/django_registration/backends/activation creating build/lib/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> build/lib/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> build/lib/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> build/lib/django_registration/backends/one_step running egg_info creating src/django_registration.egg-info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt writing manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.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 'django_registration.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 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.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) creating build/lib/django_registration/locale creating build/lib/django_registration/locale/ar creating build/lib/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> build/lib/django_registration/locale/ar/LC_MESSAGES creating build/lib/django_registration/locale/bg creating build/lib/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> build/lib/django_registration/locale/bg/LC_MESSAGES creating build/lib/django_registration/locale/ca creating build/lib/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> build/lib/django_registration/locale/ca/LC_MESSAGES creating build/lib/django_registration/locale/cs creating build/lib/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> build/lib/django_registration/locale/cs/LC_MESSAGES creating build/lib/django_registration/locale/da creating build/lib/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> build/lib/django_registration/locale/da/LC_MESSAGES creating build/lib/django_registration/locale/de creating build/lib/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> build/lib/django_registration/locale/de/LC_MESSAGES creating build/lib/django_registration/locale/el creating build/lib/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> build/lib/django_registration/locale/el/LC_MESSAGES creating build/lib/django_registration/locale/en creating build/lib/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> build/lib/django_registration/locale/en/LC_MESSAGES creating build/lib/django_registration/locale/es creating build/lib/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> build/lib/django_registration/locale/es/LC_MESSAGES creating build/lib/django_registration/locale/es_AR creating build/lib/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django_registration/locale/es_AR/LC_MESSAGES creating build/lib/django_registration/locale/fa creating build/lib/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> build/lib/django_registration/locale/fa/LC_MESSAGES creating build/lib/django_registration/locale/fr creating build/lib/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> build/lib/django_registration/locale/fr/LC_MESSAGES creating build/lib/django_registration/locale/he creating build/lib/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> build/lib/django_registration/locale/he/LC_MESSAGES creating build/lib/django_registration/locale/hr creating build/lib/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> build/lib/django_registration/locale/hr/LC_MESSAGES creating build/lib/django_registration/locale/is creating build/lib/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> build/lib/django_registration/locale/is/LC_MESSAGES creating build/lib/django_registration/locale/it creating build/lib/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> build/lib/django_registration/locale/it/LC_MESSAGES creating build/lib/django_registration/locale/ja creating build/lib/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> build/lib/django_registration/locale/ja/LC_MESSAGES creating build/lib/django_registration/locale/ko creating build/lib/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> build/lib/django_registration/locale/ko/LC_MESSAGES creating build/lib/django_registration/locale/nb creating build/lib/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> build/lib/django_registration/locale/nb/LC_MESSAGES creating build/lib/django_registration/locale/nl creating build/lib/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> build/lib/django_registration/locale/nl/LC_MESSAGES creating build/lib/django_registration/locale/pl creating build/lib/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> build/lib/django_registration/locale/pl/LC_MESSAGES creating build/lib/django_registration/locale/pt creating build/lib/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> build/lib/django_registration/locale/pt/LC_MESSAGES creating build/lib/django_registration/locale/pt_BR creating build/lib/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django_registration/locale/pt_BR/LC_MESSAGES creating build/lib/django_registration/locale/ru creating build/lib/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> build/lib/django_registration/locale/ru/LC_MESSAGES creating build/lib/django_registration/locale/sl creating build/lib/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> build/lib/django_registration/locale/sl/LC_MESSAGES creating build/lib/django_registration/locale/sr creating build/lib/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> build/lib/django_registration/locale/sr/LC_MESSAGES creating build/lib/django_registration/locale/sv creating build/lib/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> build/lib/django_registration/locale/sv/LC_MESSAGES creating build/lib/django_registration/locale/tr_TR creating build/lib/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> build/lib/django_registration/locale/tr_TR/LC_MESSAGES creating build/lib/django_registration/locale/zh_CN creating build/lib/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/django_registration/locale/zh_CN/LC_MESSAGES creating build/lib/django_registration/locale/zh_TW creating build/lib/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/django_registration/locale/zh_TW/LC_MESSAGES /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running check >>> py3-django-registration: Entering fakeroot... /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running install /usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer, pypa/build or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /home/buildozer/aports/community/py3-django-registration/pkg creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11 creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration copying build/lib/django_registration/__init__.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration copying build/lib/django_registration/signals.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration copying build/lib/django_registration/views.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration copying build/lib/django_registration/forms.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration copying build/lib/django_registration/validators.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration copying build/lib/django_registration/exceptions.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/migrations copying build/lib/django_registration/migrations/__init__.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/migrations copying build/lib/django_registration/migrations/0001_initial.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/migrations creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ca creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ca/LC_MESSAGES copying build/lib/django_registration/locale/ca/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ca/LC_MESSAGES copying build/lib/django_registration/locale/ca/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ca/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/el creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/el/LC_MESSAGES copying build/lib/django_registration/locale/el/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/el/LC_MESSAGES copying build/lib/django_registration/locale/el/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/el/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/en creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/en/LC_MESSAGES copying build/lib/django_registration/locale/en/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/en/LC_MESSAGES copying build/lib/django_registration/locale/en/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/en/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/tr_TR creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/tr_TR/LC_MESSAGES copying build/lib/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/tr_TR/LC_MESSAGES copying build/lib/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ko creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ko/LC_MESSAGES copying build/lib/django_registration/locale/ko/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ko/LC_MESSAGES copying build/lib/django_registration/locale/ko/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ko/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/is creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/is/LC_MESSAGES copying build/lib/django_registration/locale/is/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/is/LC_MESSAGES copying build/lib/django_registration/locale/is/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/is/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/bg creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/bg/LC_MESSAGES copying build/lib/django_registration/locale/bg/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/bg/LC_MESSAGES copying build/lib/django_registration/locale/bg/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/bg/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_TW creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_TW/LC_MESSAGES copying build/lib/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_TW/LC_MESSAGES copying build/lib/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ja creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ja/LC_MESSAGES copying build/lib/django_registration/locale/ja/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ja/LC_MESSAGES copying build/lib/django_registration/locale/ja/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ja/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/cs creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/cs/LC_MESSAGES copying build/lib/django_registration/locale/cs/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/cs/LC_MESSAGES copying build/lib/django_registration/locale/cs/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/cs/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sl creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sl/LC_MESSAGES copying build/lib/django_registration/locale/sl/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sl/LC_MESSAGES copying build/lib/django_registration/locale/sl/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sl/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_CN creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_CN/LC_MESSAGES copying build/lib/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_CN/LC_MESSAGES copying build/lib/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt_BR creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt_BR/LC_MESSAGES copying build/lib/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt_BR/LC_MESSAGES copying build/lib/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pl creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pl/LC_MESSAGES copying build/lib/django_registration/locale/pl/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pl/LC_MESSAGES copying build/lib/django_registration/locale/pl/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pl/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/hr creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/hr/LC_MESSAGES copying build/lib/django_registration/locale/hr/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/hr/LC_MESSAGES copying build/lib/django_registration/locale/hr/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/hr/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ru creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ru/LC_MESSAGES copying build/lib/django_registration/locale/ru/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ru/LC_MESSAGES copying build/lib/django_registration/locale/ru/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ru/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es/LC_MESSAGES copying build/lib/django_registration/locale/es/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es/LC_MESSAGES copying build/lib/django_registration/locale/es/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/de creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/de/LC_MESSAGES copying build/lib/django_registration/locale/de/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/de/LC_MESSAGES copying build/lib/django_registration/locale/de/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/de/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/it creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/it/LC_MESSAGES copying build/lib/django_registration/locale/it/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/it/LC_MESSAGES copying build/lib/django_registration/locale/it/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/it/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sr creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sr/LC_MESSAGES copying build/lib/django_registration/locale/sr/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sr/LC_MESSAGES copying build/lib/django_registration/locale/sr/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sr/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fr creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fr/LC_MESSAGES copying build/lib/django_registration/locale/fr/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fr/LC_MESSAGES copying build/lib/django_registration/locale/fr/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fr/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ar creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ar/LC_MESSAGES copying build/lib/django_registration/locale/ar/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ar/LC_MESSAGES copying build/lib/django_registration/locale/ar/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/ar/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es_AR creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es_AR/LC_MESSAGES copying build/lib/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es_AR/LC_MESSAGES copying build/lib/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/es_AR/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sv creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sv/LC_MESSAGES copying build/lib/django_registration/locale/sv/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sv/LC_MESSAGES copying build/lib/django_registration/locale/sv/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/sv/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nb creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nb/LC_MESSAGES copying build/lib/django_registration/locale/nb/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nb/LC_MESSAGES copying build/lib/django_registration/locale/nb/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nb/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nl creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nl/LC_MESSAGES copying build/lib/django_registration/locale/nl/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nl/LC_MESSAGES copying build/lib/django_registration/locale/nl/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/nl/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt/LC_MESSAGES copying build/lib/django_registration/locale/pt/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt/LC_MESSAGES copying build/lib/django_registration/locale/pt/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/pt/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/he creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/he/LC_MESSAGES copying build/lib/django_registration/locale/he/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/he/LC_MESSAGES copying build/lib/django_registration/locale/he/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/he/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fa creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fa/LC_MESSAGES copying build/lib/django_registration/locale/fa/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fa/LC_MESSAGES copying build/lib/django_registration/locale/fa/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/fa/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/da creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/da/LC_MESSAGES copying build/lib/django_registration/locale/da/LC_MESSAGES/django.po -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/da/LC_MESSAGES copying build/lib/django_registration/locale/da/LC_MESSAGES/django.mo -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/locale/da/LC_MESSAGES creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends copying build/lib/django_registration/backends/__init__.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation copying build/lib/django_registration/backends/activation/__init__.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation copying build/lib/django_registration/backends/activation/views.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation copying build/lib/django_registration/backends/activation/urls.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation creating /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step copying build/lib/django_registration/backends/one_step/__init__.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step copying build/lib/django_registration/backends/one_step/views.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step copying build/lib/django_registration/backends/one_step/urls.py -> /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/signals.py to signals.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/views.py to views.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/forms.py to forms.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/validators.py to validators.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/exceptions.py to exceptions.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation/views.py to views.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation/urls.py to urls.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step/views.py to views.cpython-311.pyc byte-compiling /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step/urls.py to urls.cpython-311.pyc running install_egg_info running egg_info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' Copying src/django_registration.egg-info to /home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration-3.3-py3.11.egg-info running install_scripts >>> py3-django-registration-pyc*: Running split function pyc... '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/__pycache__' -> '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration-pyc/usr/lib/python3.11/site-packages/django_registration/__pycache__' '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/migrations/__pycache__' -> '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration-pyc/usr/lib/python3.11/site-packages/django_registration/migrations/__pycache__' '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/__pycache__' -> '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration-pyc/usr/lib/python3.11/site-packages/django_registration/backends/__pycache__' '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/activation/__pycache__' -> '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration-pyc/usr/lib/python3.11/site-packages/django_registration/backends/activation/__pycache__' '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration/usr/lib/python3.11/site-packages/django_registration/backends/one_step/__pycache__' -> '/home/buildozer/aports/community/py3-django-registration/pkg/py3-django-registration-pyc/usr/lib/python3.11/site-packages/django_registration/backends/one_step/__pycache__' >>> py3-django-registration-pyc*: Preparing subpackage py3-django-registration-pyc... >>> py3-django-registration-pyc*: Running postcheck for py3-django-registration-pyc >>> py3-django-registration*: Running postcheck for py3-django-registration >>> py3-django-registration*: Preparing package py3-django-registration... >>> py3-django-registration-pyc*: Tracing dependencies... python3 python3~3.11 >>> py3-django-registration-pyc*: Package size: 136.0 KB >>> py3-django-registration-pyc*: Compressing data... >>> py3-django-registration-pyc*: Create checksum... >>> py3-django-registration-pyc*: Create py3-django-registration-pyc-3.3-r2.apk >>> py3-django-registration*: Tracing dependencies... python3 python3~3.11 >>> py3-django-registration*: Package size: 620.0 KB >>> py3-django-registration*: Compressing data... >>> py3-django-registration*: Create checksum... >>> py3-django-registration*: Create py3-django-registration-3.3-r2.apk >>> py3-django-registration: Build complete at Sun, 23 Apr 2023 01:37:09 +0000 elapsed time 0h 0m 3s >>> py3-django-registration: Cleaning up srcdir >>> py3-django-registration: Cleaning up pkgdir >>> py3-django-registration: Uninstalling dependencies... (1/19) Purging .makedepends-py3-django-registration (20230423.013707) (2/19) Purging py3-setuptools-pyc (67.7.1-r0) (3/19) Purging py3-setuptools (67.7.1-r0) (4/19) Purging py3-packaging-pyc (23.1-r1) (5/19) Purging py3-packaging (23.1-r1) (6/19) Purging py3-parsing-pyc (3.0.9-r2) (7/19) Purging py3-parsing (3.0.9-r2) (8/19) Purging python3-pyc (3.11.3-r10) (9/19) Purging python3-pycache-pyc0 (3.11.3-r10) (10/19) Purging pyc (0.1-r0) (11/19) Purging python3 (3.11.3-r10) (12/19) Purging gdbm (1.23-r1) (13/19) Purging libbz2 (1.0.8-r5) (14/19) Purging libffi (3.4.4-r2) (15/19) Purging libpanelw (6.4_p20230401-r5) (16/19) Purging mpdecimal (2.5.1-r2) (17/19) Purging readline (8.2.1-r1) (18/19) Purging sqlite-libs (3.41.2-r2) (19/19) Purging xz-libs (5.4.2-r1) Executing busybox-1.36.0-r7.trigger OK: 283 MiB in 98 packages >>> py3-django-registration: Updating the community/armv7 repository index... >>> py3-django-registration: Signing the index...