>>> py3-django-suit: Building testing/py3-django-suit 0.2.28-r6 (using abuild 3.11.0_rc13-r0) started Sun, 23 Apr 2023 06:22:29 +0000 >>> py3-django-suit: Checking sanity of /home/buildozer/aports/testing/py3-django-suit/APKBUILD... >>> WARNING: py3-django-suit: No maintainer >>> py3-django-suit: Analyzing dependencies... >>> py3-django-suit: 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-suit (20230423.062231) Executing busybox-1.36.0-r7.trigger OK: 441 MiB in 120 packages >>> py3-django-suit: Cleaning up srcdir >>> py3-django-suit: Cleaning up pkgdir >>> py3-django-suit: Fetching https://distfiles.alpinelinux.org/distfiles/edge/django-suit-0.2.28.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 100 604k 100 604k 0 0 1484k 0 --:--:-- --:--:-- --:--:-- 1482k >>> py3-django-suit: Fetching https://distfiles.alpinelinux.org/distfiles/edge/django-suit-0.2.28.tar.gz >>> py3-django-suit: Checking sha512sums... django-suit-0.2.28.tar.gz: OK >>> py3-django-suit: Unpacking /var/cache/distfiles/edge/django-suit-0.2.28.tar.gz... running build running build_py creating build creating build/lib creating build/lib/suit copying suit/models.py -> build/lib/suit copying suit/utils.py -> build/lib/suit copying suit/admin.py -> build/lib/suit copying suit/__init__.py -> build/lib/suit copying suit/widgets.py -> build/lib/suit copying suit/config.py -> build/lib/suit copying suit/watch_less.py -> build/lib/suit copying suit/compat.py -> build/lib/suit creating build/lib/suit/templatetags copying suit/templatetags/suit_menu.py -> build/lib/suit/templatetags copying suit/templatetags/suit_compat.py -> build/lib/suit/templatetags copying suit/templatetags/__init__.py -> build/lib/suit/templatetags copying suit/templatetags/suit_list.py -> build/lib/suit/templatetags copying suit/templatetags/suit_tags.py -> build/lib/suit/templatetags running egg_info writing django_suit.egg-info/PKG-INFO writing dependency_links to django_suit.egg-info/dependency_links.txt writing top-level names to django_suit.egg-info/top_level.txt reading manifest file 'django_suit.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'django_suit.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.admin.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.admin.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.admin.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.admin.css' to be distributed and are already explicitly excluding 'suit.static.admin.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.cms.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.cms.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.cms.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.cms.css' to be distributed and are already explicitly excluding 'suit.static.cms.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.bootstrap.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.bootstrap.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.bootstrap.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.bootstrap.css' to be distributed and are already explicitly excluding 'suit.static.suit.bootstrap.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.bootstrap.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.bootstrap.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.bootstrap.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.bootstrap.img' to be distributed and are already explicitly excluding 'suit.static.suit.bootstrap.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.bootstrap.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.bootstrap.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.bootstrap.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.bootstrap.js' to be distributed and are already explicitly excluding 'suit.static.suit.bootstrap.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.css' to be distributed and are already explicitly excluding 'suit.static.suit.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.img' to be distributed and are already explicitly excluding 'suit.static.suit.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.js' to be distributed and are already explicitly excluding 'suit.static.suit.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.static.suit.less' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.less' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.less' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.less' to be distributed and are already explicitly excluding 'suit.static.suit.less' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.static.suit.less.djangocms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.less.djangocms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.less.djangocms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.less.djangocms' to be distributed and are already explicitly excluding 'suit.static.suit.less.djangocms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.static.suit.less.ui' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.static.suit.less.ui' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.static.suit.less.ui' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.static.suit.less.ui' to be distributed and are already explicitly excluding 'suit.static.suit.less.ui' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates' to be distributed and are already explicitly excluding 'suit.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.templates.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin' to be distributed and are already explicitly excluding 'suit.templates.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.templates.admin.auth.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.auth.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.auth.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.auth.user' to be distributed and are already explicitly excluding 'suit.templates.admin.auth.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.cms.page' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.cms.page' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.cms.page' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.cms.page' to be distributed and are already explicitly excluding 'suit.templates.admin.cms.page' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.templates.admin.cms.page.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.cms.page.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.cms.page.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.cms.page.includes' to be distributed and are already explicitly excluding 'suit.templates.admin.cms.page.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.templates.admin.cms.page.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.cms.page.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.cms.page.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.cms.page.widgets' to be distributed and are already explicitly excluding 'suit.templates.admin.cms.page.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.edit_inline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.edit_inline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.edit_inline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.edit_inline' to be distributed and are already explicitly excluding 'suit.templates.admin.edit_inline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.filer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.filer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.filer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.filer' to be distributed and are already explicitly excluding 'suit.templates.admin.filer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.filer.folder' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.filer.folder' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.filer.folder' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.filer.folder' to be distributed and are already explicitly excluding 'suit.templates.admin.filer.folder' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.filer.image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.filer.image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.filer.image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.filer.image' to be distributed and are already explicitly excluding 'suit.templates.admin.filer.image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.templates.admin.filer.tools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.filer.tools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.filer.tools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.filer.tools' to be distributed and are already explicitly excluding 'suit.templates.admin.filer.tools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.filer.tools.clipboard' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.filer.tools.clipboard' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.filer.tools.clipboard' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.filer.tools.clipboard' to be distributed and are already explicitly excluding 'suit.templates.admin.filer.tools.clipboard' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.import_export' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.import_export' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.import_export' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.import_export' to be distributed and are already explicitly excluding 'suit.templates.admin.import_export' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.admin.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.admin.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.admin.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.admin.includes' to be distributed and are already explicitly excluding 'suit.templates.admin.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'suit.templates.registration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.registration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.registration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.registration' to be distributed and are already explicitly excluding 'suit.templates.registration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.reversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.reversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.reversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.reversion' to be distributed and are already explicitly excluding 'suit.templates.reversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.suit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.suit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.suit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.suit' to be distributed and are already explicitly excluding 'suit.templates.suit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'suit.templates.suit.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'suit.templates.suit.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'suit.templates.suit.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'suit.templates.suit.includes' to be distributed and are already explicitly excluding 'suit.templates.suit.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/suit/static creating build/lib/suit/static/admin creating build/lib/suit/static/admin/css copying suit/static/admin/css/forms.css -> build/lib/suit/static/admin/css creating build/lib/suit/static/cms creating build/lib/suit/static/cms/css copying suit/static/cms/css/pages.css -> build/lib/suit/static/cms/css creating build/lib/suit/static/suit creating build/lib/suit/static/suit/bootstrap creating build/lib/suit/static/suit/bootstrap/css copying suit/static/suit/bootstrap/css/bootstrap.css -> build/lib/suit/static/suit/bootstrap/css copying suit/static/suit/bootstrap/css/bootstrap.min.css -> build/lib/suit/static/suit/bootstrap/css creating build/lib/suit/static/suit/bootstrap/img copying suit/static/suit/bootstrap/img/glyphicons-halflings-white-shadow.png -> build/lib/suit/static/suit/bootstrap/img copying suit/static/suit/bootstrap/img/glyphicons-halflings-white.png -> build/lib/suit/static/suit/bootstrap/img copying suit/static/suit/bootstrap/img/glyphicons-halflings.png -> build/lib/suit/static/suit/bootstrap/img creating build/lib/suit/static/suit/bootstrap/js copying suit/static/suit/bootstrap/js/bootstrap.js -> build/lib/suit/static/suit/bootstrap/js copying suit/static/suit/bootstrap/js/bootstrap.min.js -> build/lib/suit/static/suit/bootstrap/js creating build/lib/suit/static/suit/css copying suit/static/suit/css/djangocms.css -> build/lib/suit/static/suit/css copying suit/static/suit/css/filer.css -> build/lib/suit/static/suit/css copying suit/static/suit/css/suit.css -> build/lib/suit/static/suit/css creating build/lib/suit/static/suit/img copying suit/static/suit/img/ajax-loader.gif -> build/lib/suit/static/suit/img copying suit/static/suit/img/bg_left_white.gif -> build/lib/suit/static/suit/img copying suit/static/suit/img/bg_pattern.jpg -> build/lib/suit/static/suit/img copying suit/static/suit/img/cc_active_nav.png -> build/lib/suit/static/suit/img copying suit/static/suit/img/drag-handle.png -> build/lib/suit/static/suit/img copying suit/static/suit/img/glyphicons-halflings-white-nav.png -> build/lib/suit/static/suit/img copying suit/static/suit/img/glyphicons-halflings-white-shadow.png -> build/lib/suit/static/suit/img creating build/lib/suit/static/suit/js copying suit/static/suit/js/djangocms.js -> build/lib/suit/static/suit/js copying suit/static/suit/js/jquery-1.8.3.min.js -> build/lib/suit/static/suit/js copying suit/static/suit/js/jquery-2.2.4.min.js -> build/lib/suit/static/suit/js copying suit/static/suit/js/jquery.autosize-min.js -> build/lib/suit/static/suit/js copying suit/static/suit/js/sortables.js -> build/lib/suit/static/suit/js copying suit/static/suit/js/suit-form-confirm.js -> build/lib/suit/static/suit/js copying suit/static/suit/js/suit.js -> build/lib/suit/static/suit/js creating build/lib/suit/static/suit/less copying suit/static/suit/less/djangocms.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/filer.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/footer.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/header.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/left-column.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/mixins.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/print.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/sticky-footer.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/suit.less -> build/lib/suit/static/suit/less copying suit/static/suit/less/variables.less -> build/lib/suit/static/suit/less creating build/lib/suit/static/suit/less/djangocms copying suit/static/suit/less/djangocms/list.less -> build/lib/suit/static/suit/less/djangocms creating build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/actionlist.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/box.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/breadcrumb.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/calendar.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/datepicker.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/form.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/left-nav.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/list.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/login.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/pagination.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/table.less -> build/lib/suit/static/suit/less/ui copying suit/static/suit/less/ui/tabs.less -> build/lib/suit/static/suit/less/ui creating build/lib/suit/templates copying suit/templates/403.html -> build/lib/suit/templates copying suit/templates/404.html -> build/lib/suit/templates copying suit/templates/500.html -> build/lib/suit/templates creating build/lib/suit/templates/admin copying suit/templates/admin/actions.html -> build/lib/suit/templates/admin copying suit/templates/admin/app_index.html -> build/lib/suit/templates/admin copying suit/templates/admin/base.html -> build/lib/suit/templates/admin copying suit/templates/admin/base_site.html -> build/lib/suit/templates/admin copying suit/templates/admin/change_form.html -> build/lib/suit/templates/admin copying suit/templates/admin/change_list.html -> build/lib/suit/templates/admin copying suit/templates/admin/change_list_results.html -> build/lib/suit/templates/admin copying suit/templates/admin/date_hierarchy.html -> build/lib/suit/templates/admin copying suit/templates/admin/delete_confirmation.html -> build/lib/suit/templates/admin copying suit/templates/admin/delete_selected_confirmation.html -> build/lib/suit/templates/admin copying suit/templates/admin/filter.html -> build/lib/suit/templates/admin copying suit/templates/admin/index.html -> build/lib/suit/templates/admin copying suit/templates/admin/login.html -> build/lib/suit/templates/admin copying suit/templates/admin/mptt_change_list_results.html -> build/lib/suit/templates/admin copying suit/templates/admin/object_history.html -> build/lib/suit/templates/admin copying suit/templates/admin/page_submit_line.html -> build/lib/suit/templates/admin copying suit/templates/admin/pagination.html -> build/lib/suit/templates/admin copying suit/templates/admin/search_form.html -> build/lib/suit/templates/admin copying suit/templates/admin/submit_line.html -> build/lib/suit/templates/admin creating build/lib/suit/templates/admin/auth creating build/lib/suit/templates/admin/auth/user copying suit/templates/admin/auth/user/add_form.html -> build/lib/suit/templates/admin/auth/user copying suit/templates/admin/auth/user/change_password.html -> build/lib/suit/templates/admin/auth/user creating build/lib/suit/templates/admin/cms creating build/lib/suit/templates/admin/cms/page copying suit/templates/admin/cms/page/change_form.html -> build/lib/suit/templates/admin/cms/page copying suit/templates/admin/cms/page/change_list.html -> build/lib/suit/templates/admin/cms/page copying suit/templates/admin/cms/page/plugin_change_form.html -> build/lib/suit/templates/admin/cms/page creating build/lib/suit/templates/admin/cms/page/includes copying suit/templates/admin/cms/page/includes/fieldset.html -> build/lib/suit/templates/admin/cms/page/includes creating build/lib/suit/templates/admin/cms/page/widgets copying suit/templates/admin/cms/page/widgets/plugin_item.html -> build/lib/suit/templates/admin/cms/page/widgets creating build/lib/suit/templates/admin/edit_inline copying suit/templates/admin/edit_inline/stacked.html -> build/lib/suit/templates/admin/edit_inline copying suit/templates/admin/edit_inline/tabular.html -> build/lib/suit/templates/admin/edit_inline creating build/lib/suit/templates/admin/filer copying suit/templates/admin/filer/actions.html -> build/lib/suit/templates/admin/filer copying suit/templates/admin/filer/breadcrumbs.html -> build/lib/suit/templates/admin/filer copying suit/templates/admin/filer/change_form.html -> build/lib/suit/templates/admin/filer copying suit/templates/admin/filer/delete_confirmation.html -> build/lib/suit/templates/admin/filer copying suit/templates/admin/filer/delete_selected_files_confirmation.html -> build/lib/suit/templates/admin/filer creating build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/change_form.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/choose_copy_destination.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/choose_images_resize_options.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/choose_move_destination.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/choose_rename_format.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/directory_listing.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/directory_table.html -> build/lib/suit/templates/admin/filer/folder copying suit/templates/admin/filer/folder/new_folder_form.html -> build/lib/suit/templates/admin/filer/folder creating build/lib/suit/templates/admin/filer/image copying suit/templates/admin/filer/image/change_form.html -> build/lib/suit/templates/admin/filer/image creating build/lib/suit/templates/admin/filer/tools copying suit/templates/admin/filer/tools/search_form.html -> build/lib/suit/templates/admin/filer/tools creating build/lib/suit/templates/admin/filer/tools/clipboard copying suit/templates/admin/filer/tools/clipboard/clipboard.html -> build/lib/suit/templates/admin/filer/tools/clipboard copying suit/templates/admin/filer/tools/clipboard/clipboard_item_rows.html -> build/lib/suit/templates/admin/filer/tools/clipboard creating build/lib/suit/templates/admin/import_export copying suit/templates/admin/import_export/base.html -> build/lib/suit/templates/admin/import_export copying suit/templates/admin/import_export/change_list_export.html -> build/lib/suit/templates/admin/import_export copying suit/templates/admin/import_export/change_list_import.html -> build/lib/suit/templates/admin/import_export copying suit/templates/admin/import_export/change_list_import_export.html -> build/lib/suit/templates/admin/import_export copying suit/templates/admin/import_export/export.html -> build/lib/suit/templates/admin/import_export copying suit/templates/admin/import_export/import.html -> build/lib/suit/templates/admin/import_export creating build/lib/suit/templates/admin/includes copying suit/templates/admin/includes/fieldset.html -> build/lib/suit/templates/admin/includes creating build/lib/suit/templates/registration copying suit/templates/registration/logged_out.html -> build/lib/suit/templates/registration copying suit/templates/registration/password_change_form.html -> build/lib/suit/templates/registration creating build/lib/suit/templates/reversion copying suit/templates/reversion/change_list.html -> build/lib/suit/templates/reversion copying suit/templates/reversion/object_history.html -> build/lib/suit/templates/reversion copying suit/templates/reversion/recover_form.html -> build/lib/suit/templates/reversion copying suit/templates/reversion/recover_list.html -> build/lib/suit/templates/reversion copying suit/templates/reversion/revision_form.html -> build/lib/suit/templates/reversion creating build/lib/suit/templates/suit copying suit/templates/suit/error_base.html -> build/lib/suit/templates/suit copying suit/templates/suit/form_as_fieldset.html -> build/lib/suit/templates/suit copying suit/templates/suit/menu.html -> build/lib/suit/templates/suit creating build/lib/suit/templates/suit/includes copying suit/templates/suit/includes/change_form_includes.html -> build/lib/suit/templates/suit/includes >>> py3-django-suit: Entering fakeroot... 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/testing/py3-django-suit/pkg creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11 creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit copying build/lib/suit/models.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit copying build/lib/suit/utils.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/includes copying build/lib/suit/templates/admin/includes/fieldset.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/includes creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/import_export/base.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/import_export/export.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/import_export/change_list_export.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/import_export/import.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/import_export/change_list_import.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/import_export/change_list_import_export.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/import_export copying build/lib/suit/templates/admin/app_index.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/base.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/auth creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/auth/user copying build/lib/suit/templates/admin/auth/user/change_password.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/auth/user copying build/lib/suit/templates/admin/auth/user/add_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/auth/user creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/edit_inline copying build/lib/suit/templates/admin/edit_inline/stacked.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/edit_inline copying build/lib/suit/templates/admin/edit_inline/tabular.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/edit_inline copying build/lib/suit/templates/admin/submit_line.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/change_list.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/actions.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer copying build/lib/suit/templates/admin/filer/delete_selected_files_confirmation.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer copying build/lib/suit/templates/admin/filer/actions.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/image copying build/lib/suit/templates/admin/filer/image/change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/image copying build/lib/suit/templates/admin/filer/change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer copying build/lib/suit/templates/admin/filer/breadcrumbs.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/tools creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/tools/clipboard copying build/lib/suit/templates/admin/filer/tools/clipboard/clipboard_item_rows.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/tools/clipboard copying build/lib/suit/templates/admin/filer/tools/clipboard/clipboard.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/tools/clipboard copying build/lib/suit/templates/admin/filer/tools/search_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/tools copying build/lib/suit/templates/admin/filer/delete_confirmation.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/choose_copy_destination.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/choose_images_resize_options.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/new_folder_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/directory_listing.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/choose_move_destination.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/directory_table.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filer/folder/choose_rename_format.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/filer/folder copying build/lib/suit/templates/admin/filter.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/delete_selected_confirmation.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/search_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/index.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/date_hierarchy.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/base_site.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/object_history.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/delete_confirmation.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/mptt_change_list_results.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/page_submit_line.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/login.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/pagination.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin copying build/lib/suit/templates/admin/change_list_results.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page/includes copying build/lib/suit/templates/admin/cms/page/includes/fieldset.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page/includes copying build/lib/suit/templates/admin/cms/page/plugin_change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page copying build/lib/suit/templates/admin/cms/page/change_list.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page/widgets copying build/lib/suit/templates/admin/cms/page/widgets/plugin_item.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page/widgets copying build/lib/suit/templates/admin/cms/page/change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/admin/cms/page creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/reversion copying build/lib/suit/templates/reversion/recover_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/reversion copying build/lib/suit/templates/reversion/change_list.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/reversion copying build/lib/suit/templates/reversion/revision_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/reversion copying build/lib/suit/templates/reversion/object_history.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/reversion copying build/lib/suit/templates/reversion/recover_list.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/reversion creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/registration copying build/lib/suit/templates/registration/logged_out.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/registration copying build/lib/suit/templates/registration/password_change_form.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/registration creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/suit creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/suit/includes copying build/lib/suit/templates/suit/includes/change_form_includes.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/suit/includes copying build/lib/suit/templates/suit/error_base.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/suit copying build/lib/suit/templates/suit/form_as_fieldset.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/suit copying build/lib/suit/templates/suit/menu.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates/suit copying build/lib/suit/templates/500.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates copying build/lib/suit/templates/403.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates copying build/lib/suit/templates/404.html -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templates copying build/lib/suit/admin.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags copying build/lib/suit/templatetags/suit_menu.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags copying build/lib/suit/templatetags/suit_compat.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags copying build/lib/suit/templatetags/__init__.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags copying build/lib/suit/templatetags/suit_list.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags copying build/lib/suit/templatetags/suit_tags.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags copying build/lib/suit/__init__.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/admin creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/admin/css copying build/lib/suit/static/admin/css/forms.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/admin/css creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/sortables.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/djangocms.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/suit.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/jquery-1.8.3.min.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/suit-form-confirm.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/jquery.autosize-min.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js copying build/lib/suit/static/suit/js/jquery-2.2.4.min.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/js creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/css copying build/lib/suit/static/suit/css/suit.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/css copying build/lib/suit/static/suit/css/djangocms.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/css copying build/lib/suit/static/suit/css/filer.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/css creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/cc_active_nav.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/glyphicons-halflings-white-nav.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/bg_pattern.jpg -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/ajax-loader.gif -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/glyphicons-halflings-white-shadow.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/bg_left_white.gif -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img copying build/lib/suit/static/suit/img/drag-handle.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/img creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/js copying build/lib/suit/static/suit/bootstrap/js/bootstrap.min.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/js copying build/lib/suit/static/suit/bootstrap/js/bootstrap.js -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/js creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/css copying build/lib/suit/static/suit/bootstrap/css/bootstrap.min.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/css copying build/lib/suit/static/suit/bootstrap/css/bootstrap.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/css creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/img copying build/lib/suit/static/suit/bootstrap/img/glyphicons-halflings-white.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/img copying build/lib/suit/static/suit/bootstrap/img/glyphicons-halflings-white-shadow.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/img copying build/lib/suit/static/suit/bootstrap/img/glyphicons-halflings.png -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/bootstrap/img creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/djangocms.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/filer.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/left-column.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/box.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/table.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/calendar.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/tabs.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/pagination.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/form.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/breadcrumb.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/actionlist.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/list.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/datepicker.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/left-nav.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/ui/login.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/ui copying build/lib/suit/static/suit/less/mixins.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/variables.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/footer.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/suit.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/djangocms copying build/lib/suit/static/suit/less/djangocms/list.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less/djangocms copying build/lib/suit/static/suit/less/sticky-footer.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/print.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less copying build/lib/suit/static/suit/less/header.less -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/suit/less creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/cms creating /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/cms/css copying build/lib/suit/static/cms/css/pages.css -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/static/cms/css copying build/lib/suit/widgets.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit copying build/lib/suit/config.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit copying build/lib/suit/watch_less.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit copying build/lib/suit/compat.py -> /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/models.py to models.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/utils.py to utils.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/admin.py to admin.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags/suit_menu.py to suit_menu.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags/suit_compat.py to suit_compat.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags/suit_list.py to suit_list.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags/suit_tags.py to suit_tags.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/widgets.py to widgets.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/config.py to config.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/watch_less.py to watch_less.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/compat.py to compat.cpython-311.pyc running install_egg_info running egg_info writing django_suit.egg-info/PKG-INFO writing dependency_links to django_suit.egg-info/dependency_links.txt writing top-level names to django_suit.egg-info/top_level.txt reading manifest file 'django_suit.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'django_suit.egg-info/SOURCES.txt' Copying django_suit.egg-info to /home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/django_suit-0.2.28-py3.11.egg-info running install_scripts >>> py3-django-suit-pyc*: Running split function pyc... '/home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/templatetags/__pycache__' -> '/home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit-pyc/usr/lib/python3.11/site-packages/suit/templatetags/__pycache__' '/home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit/usr/lib/python3.11/site-packages/suit/__pycache__' -> '/home/buildozer/aports/testing/py3-django-suit/pkg/py3-django-suit-pyc/usr/lib/python3.11/site-packages/suit/__pycache__' >>> py3-django-suit-pyc*: Preparing subpackage py3-django-suit-pyc... >>> py3-django-suit-pyc*: Running postcheck for py3-django-suit-pyc >>> py3-django-suit*: Running postcheck for py3-django-suit >>> py3-django-suit*: Preparing package py3-django-suit... >>> py3-django-suit-pyc*: Tracing dependencies... python3 python3~3.11 >>> py3-django-suit-pyc*: Package size: 140.0 KB >>> py3-django-suit-pyc*: Compressing data... >>> py3-django-suit-pyc*: Create checksum... >>> py3-django-suit-pyc*: Create py3-django-suit-pyc-0.2.28-r6.apk >>> py3-django-suit*: Tracing dependencies... python3 python3~3.11 >>> py3-django-suit*: Package size: 1.5 MB >>> py3-django-suit*: Compressing data... >>> py3-django-suit*: Create checksum... >>> py3-django-suit*: Create py3-django-suit-0.2.28-r6.apk >>> py3-django-suit: Build complete at Sun, 23 Apr 2023 06:22:34 +0000 elapsed time 0h 0m 5s >>> py3-django-suit: Cleaning up srcdir >>> py3-django-suit: Cleaning up pkgdir >>> py3-django-suit: Uninstalling dependencies... (1/19) Purging .makedepends-py3-django-suit (20230423.062231) (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: 393 MiB in 101 packages >>> py3-django-suit: Updating the testing/x86_64 repository index... >>> py3-django-suit: Signing the index...