Building package "chirp-next" INFO: Starting build... INFO: Verifying bootstrap image /home/u726578/chaotic/cache/lower/20240503074035.sif WARNING: integrity: signature not found for object group 1 WARNING: Bootstrap image could not be verified, but build will continue. INFO: Creating sandbox directory... INFO: Build complete: /scratch/chaotic/sandbox/pkg45c1e8fccf3 :: Synchronizing package databases... core downloading... extra downloading... multilib downloading... chaotic-aur downloading... :: Starting full system upgrade... there is nothing to do resolving dependencies... :: There are 2 providers available for libgl: :: Repository extra 1) libglvnd :: Repository chaotic-aur 2) nvidia-340xx-utils Enter a number (default=1): looking for conflicting packages... warning: dependency cycle detected: warning: harfbuzz will be installed before its freetype2 dependency warning: dependency cycle detected: warning: mesa will be installed before its libglvnd dependency Packages (132) adobe-source-code-pro-fonts-2.042u+1.062i+1.026vf-1 adwaita-cursors-46.0-1 adwaita-icon-theme-46.0-1 at-spi2-core-2.52.0-1 avahi-1:0.8+r194+g3f79789-2 cairo-1.18.0-2 cantarell-fonts-1:0.303.1-1 dconf-0.40.0-2 default-cursors-2-1 desktop-file-utils-0.27-1 duktape-2.7.0-6 fontconfig-2:2.15.0-2 freetype2-2.13.2-1 fribidi-1.0.14-1 gdk-pixbuf2-2.42.11-2 glib-networking-1:2.80.0-1 graphite-1:1.3.14-3 gsettings-desktop-schemas-46.0-1 gssdp-1.6.3-1 gst-plugins-bad-libs-1.24.3-1 gst-plugins-base-libs-1.24.3-1 gstreamer-1.24.3-1 gtk-update-icon-cache-1:4.14.4-1 gtk3-1:3.24.41-1 gupnp-1:1.6.6-1 gupnp-igd-1.6.0-1 harfbuzz-8.4.0-1 hicolor-icon-theme-0.17-3 hidapi-0.14.0-2 iso-codes-4.16.0-1 jbigkit-2.1-7 json-glib-1.8.0-1 lcms2-2.16-1 libcloudproviders-0.3.6-1 libcolord-1.4.7-2 libcups-1:2.4.8-1 libdaemon-0.14-5 libdatrie-0.2.13-4 libdrm-2.4.120-1 libedit-20230828_3.1-1 libei-1.2.1-1 libepoxy-1.5.10-2 libevdev-1.13.1-1 libglvnd-1.7.0-1 libgudev-238-1 libice-1.1.1-2 libjpeg-turbo-3.0.2-2 libmspack-1:1.11-1 libnice-0.1.22-1 libnotify-0.8.3-1 libomxil-bellagio-0.9.3-4 libpciaccess-0.18.1-2 libpng-1.6.43-1 libproxy-0.5.6-1 librsvg-2:2.58.0-1 libsm-1.2.4-1 libsoup3-3.4.4-1 libstemmer-2.2.0-2 libthai-0.1.29-3 libtiff-4.6.0-4 libunwind-1.8.1-2 libva-2.21.0-1 libx11-1.8.9-1 libxau-1.0.11-2 libxcb-1.17.0-1 libxcomposite-0.4.6-1 libxcursor-1.2.2-1 libxdamage-1.1.6-1 libxdmcp-1.1.5-1 libxext-1.3.6-1 libxfixes-6.0.1-1 libxft-2.3.8-1 libxi-1.8.1-1 libxinerama-1.1.5-1 libxkbcommon-1.7.0-2 libxkbcommon-x11-1.7.0-2 libxrandr-1.5.4-1 libxrender-0.9.11-1 libxshmfence-1.3.2-1 libxtst-1.2.4-1 libxv-1.0.12-1 libxxf86vm-1.1.5-1 llvm-libs-17.0.6-4 lm_sensors-1:3.6.0.r41.g31d1f125-2 lzo-2.10-5 mesa-1:24.0.6-2 mpdecimal-4.0.0-2 orc-0.4.38-1 pango-1:1.52.2-1 pixman-0.43.4-1 python-3.12.3-1 python-autocommand-2.2.2-6 python-charset-normalizer-3.3.2-2 python-fastjsonschema-2.19.1-3 python-idna-3.6-2 python-inflect-7.2.1-2 python-jaraco.context-4.3.0-4 python-jaraco.functools-4.0.0-3 python-jaraco.text-3.12.0-3 python-more-itertools-10.2.0-2 python-ordered-set-4.1.0-5 python-packaging-23.2-3 python-platformdirs-4.2.0-3 python-pyproject-hooks-1.1.0-1 python-tomli-2.0.1-4 python-trove-classifiers-2024.4.10-1 python-typeguard-4.2.1-2 python-typing_extensions-4.11.0-1 python-urllib3-1.26.18-3 python-validate-pyproject-0.16-1 sdl2-2.30.3-1 shared-mime-info-2.4-1 tracker3-3.7.3-1 vulkan-icd-loader-1.3.279-1 wayland-1.22.0-1 wxwidgets-common-3.2.4-4 wxwidgets-gtk3-3.2.4-4 xcb-proto-1.17.0-2 xkeyboard-config-2.41-1 xorg-xprop-1.2.7-1 xorgproto-2024.1-2 python-build-1.2.1-3 python-future-1.0.0-1 python-installer-0.7.0-8 python-pyserial-3.5-6 python-requests-2.31.0-3 python-setuptools-1:69.0.3-6 python-six-1.16.0-9 python-suds-1.4.2.0-3 python-wheel-0.43.0-4 python-wxpython-1:4.2.1-2 python-yattag-1.15.1-1.1 Total Download Size: 9.53 MiB Total Installed Size: 624.83 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... python-wxpython-1:4.2.1-2-x86_64 downloading... python-suds-1.4.2.0-3-any downloading... python-yattag-1.15.1-1.1-any downloading... checking keyring... checking package integrity... loading package files... checking for file conflicts... checking available disk space... :: Processing package changes... installing mpdecimal... installing python... Optional dependencies for python python-setuptools: for building Python packages using tooling that is usually bundled with Python [pending] python-pip: for installing Python packages using tooling that is usually bundled with Python python-pipx: for installing Python software not packaged on Arch Linux sqlite: for a default database integration [installed] xz: for lzma [installed] tk: for tkinter installing python-six... installing python-pyserial... installing python-future... Optional dependencies for python-future python-setuptools: futurize and pasteurize scripts [pending] installing python-charset-normalizer... installing python-idna... installing python-urllib3... Optional dependencies for python-urllib3 python-brotli: Brotli support python-certifi: security support python-cryptography: security support python-idna: security support [installed] python-pyopenssl: security support python-pysocks: SOCKS support installing python-requests... Optional dependencies for python-requests python-chardet: alternative character encoding library python-pysocks: SOCKS proxy support installing python-suds... installing python-yattag... installing libpng... installing graphite... Optional dependencies for graphite graphite-docs: Documentation installing harfbuzz... Optional dependencies for harfbuzz harfbuzz-utils: utilities installing freetype2... installing fontconfig... Creating fontconfig configuration... Rebuilding fontconfig cache... installing xcb-proto... installing xorgproto... installing libxdmcp... installing libxau... installing libxcb... installing libx11... installing libxext... installing libxrender... installing lzo... installing pixman... installing cairo... installing libjpeg-turbo... Optional dependencies for libjpeg-turbo java-runtime>11: for TurboJPEG Java wrapper installing jbigkit... installing libtiff... Optional dependencies for libtiff freeglut: for using tiffgt installing shared-mime-info... installing gdk-pixbuf2... Optional dependencies for gdk-pixbuf2 libwmf: Load .wmf and .apm libopenraw: Load .dng, .cr2, .crw, .nef, .orf, .pef, .arw, .erf, .mrw, and .raf libavif: Load .avif libheif: Load .heif, .heic, and .avif libjxl: Load .jxl librsvg: Load .svg, .svgz, and .svg.gz [pending] webp-pixbuf-loader: Load .webp installing libunwind... installing gstreamer... Optional dependencies for gstreamer python: gst-plugins-doc-cache-generator [installed] installing iso-codes... installing libpciaccess... installing libdrm... Optional dependencies for libdrm cairo: needed for modetest tool [installed] installing libxfixes... installing libxshmfence... installing libxxf86vm... installing libedit... installing llvm-libs... installing lm_sensors... Optional dependencies for lm_sensors rrdtool: for logging with sensord perl: for sensor detection and configuration convert [installed] installing default-cursors... Optional dependencies for default-cursors adwaita-cursors: default cursor theme [pending] installing wayland... installing libomxil-bellagio... installing mesa... Optional dependencies for mesa opengl-man-pages: for the OpenGL API man pages installing libglvnd... installing libgudev... installing libxi... installing libxv... installing orc... installing gst-plugins-base-libs... installing adobe-source-code-pro-fonts... installing cantarell-fonts... installing dconf... installing gsettings-desktop-schemas... installing duktape... installing libproxy... installing glib-networking... installing libsoup3... Optional dependencies for libsoup3 samba: Windows Domain SSO installing gssdp... Optional dependencies for gssdp gtk4: gssdp-device-sniffer installing gupnp... Optional dependencies for gupnp python: gupnp-binding-tool [installed] installing gupnp-igd... installing libnice... Optional dependencies for libnice gstreamer: "nice" GStreamer plugin [installed] installing libva... Optional dependencies for libva intel-media-driver: backend for Intel GPUs (>= Broadwell) libva-intel-driver: backend for Intel GPUs (<= Haswell) libva-mesa-driver: backend for AMD and NVIDIA GPUs installing xkeyboard-config... installing libxkbcommon... Optional dependencies for libxkbcommon libxkbcommon-x11: xkbcli interactive-x11 [pending] wayland: xkbcli interactive-wayland [installed] installing libxkbcommon-x11... installing vulkan-icd-loader... Optional dependencies for vulkan-icd-loader vulkan-driver: packaged vulkan driver installing gst-plugins-bad-libs... installing hicolor-icon-theme... installing fribidi... installing libdatrie... installing libthai... installing libxft... installing pango... installing librsvg... installing gtk-update-icon-cache... installing adwaita-cursors... installing adwaita-icon-theme... installing libevdev... installing libei... installing libxtst... installing xorg-xprop... installing at-spi2-core... Optional dependencies for at-spi2-core dbus-broker: Alternative bus implementation [installed] installing desktop-file-utils... installing libcloudproviders... installing lcms2... installing libcolord... installing libdaemon... installing avahi... Optional dependencies for avahi gtk3: avahi-discover, avahi-discover-standalone, bshell, bssh, bvnc [pending] libevent: libevent bindings [installed] nss-mdns: NSS support for mDNS python-dbus: avahi-bookmarks, avahi-discover python-gobject: avahi-bookmarks, avahi-discover python-twisted: avahi-bookmarks qt5-base: qt5 bindings installing libcups... installing libepoxy... installing libxcomposite... installing libxcursor... installing libxdamage... installing libxinerama... installing libxrandr... installing json-glib... installing libstemmer... installing tracker3... Optional dependencies for tracker3 libsoup: Alternative remoting backend installing gtk3... Optional dependencies for gtk3 evince: Default print preview command installing libnotify... installing libmspack... installing libice... installing libsm... installing hidapi... Optional dependencies for hidapi libusb: for hidapi-libusb [installed] installing sdl2... Optional dependencies for sdl2 alsa-lib: ALSA audio driver libpulse: PulseAudio audio driver jack: JACK audio driver pipewire: PipeWire audio driver libdecor: Wayland client decorations installing wxwidgets-common... installing wxwidgets-gtk3... Optional dependencies for wxwidgets-gtk3 webkit2gtk: for webview support installing python-wxpython... Optional dependencies for python-wxpython python-pypubsub: Alternative to the deprecated wx.lib.pubsub API installing python-packaging... installing python-pyproject-hooks... installing python-build... Optional dependencies for python-build python-pip: to use as the Python package installer (default) python-uv: to use as the Python package installer python-virtualenv: to use virtualenv for build isolation installing python-installer... installing python-wheel... Optional dependencies for python-wheel python-keyring: for wheel.signatures python-xdg: for wheel.signatures installing python-more-itertools... installing python-jaraco.functools... installing python-jaraco.context... installing python-autocommand... installing python-typing_extensions... installing python-typeguard... installing python-inflect... installing python-jaraco.text... installing python-ordered-set... installing python-platformdirs... installing python-tomli... installing python-fastjsonschema... installing python-trove-classifiers... installing python-validate-pyproject... installing python-setuptools... :: Running post-transaction hooks... ( 1/14) Creating system user accounts... Creating group 'avahi' with GID 973. Creating user 'avahi' (Avahi mDNS/DNS-SD daemon) with UID 973 and GID 973. ( 2/14) Reloading system manager configuration... Skipped: Current root is not booted. ( 3/14) Reloading user manager configuration... Skipped: Current root is not booted. ( 4/14) Arming ConditionNeedsUpdate... ( 5/14) Updating the MIME type database... ( 6/14) Updating fontconfig configuration... ( 7/14) Reloading system bus configuration... Skipped: Current root is not booted. ( 8/14) Updating fontconfig cache... ( 9/14) Probing GDK-Pixbuf loader modules... (10/14) Updating GIO module cache... (11/14) Compiling GSettings XML schema files... (12/14) Probing GTK3 input method modules... (13/14) Updating icon theme caches... (14/14) Updating the desktop file MIME type cache... ==> Making package: chirp-next 20240427-1 (Fri 03 May 2024 07:44:51 AM -03) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading chirp-next-20240427.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 1 1948k 1 39852 0 0 22862 0 0:01:27 0:00:01 0:01:26 22850 49 1948k 49 960k 0 0 357k 0 0:00:05 0:00:02 0:00:03 356k 100 1948k 100 1948k 0 0 676k 0 0:00:02 0:00:02 --:--:-- 676k ==> WARNING: Skipping verification of source file PGP signatures. ==> Validating source files with sha1sums... chirp-next-20240427.tar.gz ... Passed ==> Extracting sources... -> Extracting chirp-next-20240427.tar.gz with bsdtar ==> Starting build()... * Getting build dependencies for wheel... warning: no previously-included files found matching 'chirp/locale/*' * Building wheel... warning: no previously-included files found matching 'chirp/locale/*' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.en_US.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.en_US.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.en_US.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.en_US.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.en_US.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.ja_JP.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.ja_JP.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.ja_JP.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.ja_JP.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.ja_JP.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.uk_UA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.uk_UA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.uk_UA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.uk_UA.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.uk_UA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'chirp.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.share' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.share' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.share' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.share' to be distributed and are already explicitly excluding 'chirp.share' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'chirp.stock_configs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'chirp.stock_configs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'chirp.stock_configs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'chirp.stock_configs' to be distributed and are already explicitly excluding 'chirp.stock_configs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) Successfully built chirp-20240427-py3-none-any.whl ==> Entering fakeroot environment... ==> Starting package()... ==> Tidying install... -> Removing empty directories... -> Removing libtool files... -> Purging unwanted files... -> Removing static library files... -> Stripping unneeded symbols from binaries and libraries... -> Compressing man and info pages... ==> Checking for packaging issues... ==> Creating package "chirp-next"... -> Generating .PKGINFO file... -> Generating .BUILDINFO file... -> Adding install file... -> Generating .MTREE file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: chirp-next 20240427-1 (Fri 03 May 2024 07:45:03 AM -03) real 1m40.391s user 0m19.305s sys 0m48.780s