Building package "zapzap" INFO: Starting build... INFO: Verifying bootstrap image /home/u726578/chaotic/cache/lower/20240713000259.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/pkg8586a6d4840 :: 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): :: There are 2 providers available for jack: :: Repository extra 1) jack2 2) pipewire-jack Enter a number (default=1): :: There are 12 providers available for ttf-font: :: Repository extra 1) gnu-free-fonts 2) noto-fonts 3) ttf-bitstream-vera 4) ttf-croscore 5) ttf-dejavu 6) ttf-droid 7) ttf-ibm-plex 8) ttf-input 9) ttf-liberation 10) ttf-mona-sans :: Repository chaotic-aur 11) apple-fonts 12) ttf-ms-fonts 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 (203) alsa-lib-1.2.12-1 alsa-topology-conf-1.2.5.1-4 alsa-ucm-conf-1.2.12-1 aom-3.9.1-1 avahi-1:0.8+r194+g3f79789-2 cairo-1.18.0-2 dav1d-1.4.3-1 default-cursors-2-2 double-conversion-3.3.0-2 duktape-2.7.0-7 ffmpeg-2:7.0.1-2 fftw-3.3.10-7 flac-1.4.3-2 fontconfig-2:2.15.0-2 freetype2-2.13.2-2 fribidi-1.0.15-1 gdk-pixbuf2-2.42.12-1 giflib-5.2.2-1 glslang-14.2.0-1 gnu-free-fonts-20120503-8 gperftools-2.15-1 graphite-1:1.3.14-4 gsm-1.0.22-2 harfbuzz-9.0.0-1 hicolor-icon-theme-0.18-1 hidapi-0.14.0-2 highway-1.2.0-1 imath-3.1.11-2 jack2-1.9.22-1 jbigkit-2.1-8 l-smash-2.14.5-4 lame-3.100-5 lcms2-2.16-1 libass-0.17.3-1 libasyncns-1:0.8+r3+g68cd5af-3 libavc1394-0.5.4-6 libb2-0.98.1-3 libbluray-1.3.4-1 libbs2b-3.1.0-9 libcups-2:2.4.10-1 libdaemon-0.14-6 libdatrie-0.2.13-4 libdeflate-1.20-2 libdovi-3.3.0-2 libdrm-2.4.122-1 libdvdnav-6.1.1-2 libdvdread-6.1.3-2 libedit-20240517_3.1-1 libevdev-1.13.2-1 libglvnd-1.7.0-1 libgudev-238-1 libice-1.1.1-3 libiec61883-1.2.0-8 libinput-1.26.1-1 libjpeg-turbo-3.0.3-1 libjxl-0.10.3-1 libmodplug-0.8.9.0-6 libogg-1.3.5-2 libomxil-bellagio-0.9.3-5 libopenmpt-0.7.8-1 libpciaccess-0.18.1-2 libplacebo-7.349.0-1 libpng-1.6.43-1 libproxy-0.5.7-1 libpulse-17.0-3 libraw1394-2.1.2-4 librsvg-2:2.58.2-1 libsamplerate-0.2.2-3 libsm-1.2.4-2 libsndfile-1.2.2-2 libsoxr-0.1.3-4 libssh-0.10.6-2 libthai-0.1.29-3 libtheora-1.1.1-6 libtiff-4.6.0-5 libunibreak-6.1-1 libunwind-1.8.1-3 libva-2.21.0-1 libvdpau-1.5-3 libvorbis-1.3.7-3 libvpl-2.12.0-1 libvpx-1.14.0-1 libwacom-2.12.2-1 libwebp-1.4.0-1 libx11-1.8.9-1 libxau-1.0.11-3 libxcb-1.17.0-1 libxcomposite-0.4.6-2 libxcursor-1.2.2-1 libxdamage-1.1.6-2 libxdmcp-1.1.5-1 libxext-1.3.6-1 libxfixes-6.0.1-2 libxft-2.3.8-2 libxi-1.8.1-2 libxkbcommon-1.7.0-2 libxkbcommon-x11-1.7.0-2 libxkbfile-1.1.3-1 libxmu-1.2.1-1 libxrandr-1.5.4-1 libxrender-0.9.11-2 libxshmfence-1.3.2-2 libxslt-1.1.42-1 libxt-1.3.0-2 libxtst-1.2.4-2 libxv-1.0.12-2 libxxf86vm-1.1.5-2 llvm-libs-18.1.8-3 lm_sensors-1:3.6.0.r41.g31d1f125-3 lzo-2.10-5 mbedtls2-2.28.8-3 md4c-0.5.2-1 mesa-1:24.1.3-1 minizip-1:1.3.1-2 mpdecimal-4.0.0-2 mpg123-1.32.6-1 mtdev-1.1.7-1 nspr-4.35-3 nss-3.102-1 ocl-icd-2.3.2-2 opencore-amr-0.1.6-2 openexr-3.2.4-1 openjpeg2-2.5.2-1 opus-1.5.2-1 pango-1:1.54.0-1 perl-error-0.17029-6 perl-mailtools-2.21-8 perl-timedate-2.33-5 pixman-0.43.4-1 portaudio-1:19.7.0-2 python-3.12.4-1 python-annotated-types-0.7.0-1 python-autocommand-2.2.2-6 python-fastjsonschema-2.20.0-1 python-jaraco.context-4.3.0-4 python-jaraco.functools-4.0.1-1 python-more-itertools-10.3.0-1 python-ordered-set-4.1.0-5 python-packaging-24.1-1 python-platformdirs-4.2.2-1 python-pydantic-core-1:2.20.1-1 python-pyproject-hooks-1.1.0-1 python-pyqt6-sip-13.6.0-2 python-tomli-2.0.1-4 python-trove-classifiers-2024.5.22-1 python-typeguard-4.3.0-1 python-validate-pyproject-0.18-1 qt6-base-6.7.2-1 qt6-declarative-6.7.2-1 qt6-positioning-6.7.2-1 qt6-translations-6.7.2-1 qt6-webchannel-6.7.2-1 qt6-webengine-6.7.2-1 rav1e-0.7.1-1 rubberband-3.3.0-1 sdl2-2.30.5-1 shaderc-2024.1-1 shared-mime-info-2.4-1 snappy-1.1.10-1 speex-1.2.1-1 speexdsp-1.2.1-1 spirv-tools-2024.2-1 srt-1.5.3-1 svt-av1-2.1.0-1 tslib-1.23-1 v4l-utils-1.26.1-1 vapoursynth-R69-1 vid.stab-1.1.1-1 vmaf-3.0.0-1 vulkan-headers-1:1.3.285-1 vulkan-icd-loader-1.3.285-1 wayland-1.23.0-1 x264-3:0.164.r3108.31e19f9-2 x265-3.6-1 xcb-proto-1.17.0-2 xcb-util-0.4.1-2 xcb-util-cursor-0.1.5-1 xcb-util-image-0.4.1-3 xcb-util-keysyms-0.4.1-5 xcb-util-renderutil-0.3.10-2 xcb-util-wm-0.4.2-2 xdg-utils-1.2.1-1 xkeyboard-config-2.42-1 xorg-xprop-1.2.7-1 xorg-xset-1.2.5-1 xorgproto-2024.1-2 xvidcore-1.3.7-2 xxhash-0.8.2-1 zimg-3.0.5-1 desktop-file-utils-0.27-1 git-2.45.2-1 python-build-1.2.1-3 python-dbus-1.3.2-4 python-inflect-7.3.1-1 python-installer-0.7.0-8 python-jaraco.text-3.12.1-1 python-pydantic-2.8.2-1 python-pyqt6-6.7.0-4 python-pyqt6-webengine-6.7.0-2 python-setuptools-1:69.5.1-1 python-typing_extensions-4.12.2-1 python-wheel-0.43.0-4 qt6-wayland-6.7.2-2 Total Installed Size: 1152.76 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... checking available disk space... :: Processing package changes... installing double-conversion... 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 libb2... installing libdaemon... installing avahi... Optional dependencies for avahi gtk3: avahi-discover, avahi-discover-standalone, bshell, bssh, bvnc libevent: libevent bindings [installed] nss-mdns: NSS support for mDNS python-dbus: avahi-bookmarks, avahi-discover [pending] python-gobject: avahi-bookmarks, avahi-discover python-twisted: avahi-bookmarks qt5-base: qt5 bindings installing libcups... installing libpciaccess... installing libdrm... Optional dependencies for libdrm cairo: needed for modetest tool [pending] installing xcb-proto... installing xorgproto... installing libxdmcp... installing libxau... installing libxcb... installing libx11... installing libxext... 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 installing wayland... installing libomxil-bellagio... installing mesa... Optional dependencies for mesa opengl-man-pages: for the OpenGL API man pages installing libglvnd... installing libice... installing mtdev... installing libevdev... installing libgudev... installing libwacom... Optional dependencies for libwacom python-libevdev: for libwacom-show-stylus python-pyudev: for libwacom-show-stylus installing libinput... Optional dependencies for libinput gtk4: libinput debug-gui python-pyudev: libinput measure python-libevdev: libinput measure python-yaml: used by various tools installing libjpeg-turbo... Optional dependencies for libjpeg-turbo java-runtime>11: for TurboJPEG Java wrapper installing duktape... installing libproxy... installing libsm... installing xkeyboard-config... installing libxkbcommon... Optional dependencies for libxkbcommon libxkbcommon-x11: xkbcli interactive-x11 [pending] wayland: xkbcli interactive-wayland [installed] installing libxkbcommon-x11... installing md4c... installing shared-mime-info... installing tslib... installing vulkan-headers... installing xcb-util-renderutil... installing xcb-util... installing xcb-util-image... installing xcb-util-cursor... installing xcb-util-keysyms... installing xcb-util-wm... installing libxt... installing libxmu... installing xorg-xset... installing xorg-xprop... installing xdg-utils... Optional dependencies for xdg-utils kde-cli-tools: for KDE Plasma5 support in xdg-open exo: for Xfce support in xdg-open pcmanfm: for LXDE support in xdg-open perl-file-mimeinfo: for generic support in xdg-open perl-net-dbus: Perl extension to dbus used in xdg-screensaver perl-x11-protocol: Perl X11 protocol used in xdg-screensaver installing qt6-translations... installing qt6-base... Optional dependencies for qt6-base freetds: MS SQL driver gdk-pixbuf2: GTK platform plugin [pending] gtk3: GTK platform plugin libfbclient: Firebird/iBase driver mariadb-libs: MariaDB driver pango: GTK platform plugin [pending] perl: for syncqt [installed] postgresql-libs: PostgreSQL driver qt6-wayland: to run Qt6 applications in a Wayland session [pending] unixodbc: ODBC driver 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-pyqt6-sip... installing python-pyqt6... Optional dependencies for python-pyqt6 qt6-tools: QtHelp, QtDesigner bindings qt6-svg: QtSvg bindings qt6-declarative: QtQml bindings, qmlplugin [pending] qt6-quick3d: QtQuick3D bindings qt6-connectivity: QtBluetooth, QtNfc bindings qt6-multimedia: QtMultimedia, QtSpatialAudio bindings qt6-positioning: QtPositioning bindings [pending] qt6-remoteobjects: QtRemoteObjects bindings qt6-sensors: QtSensors bindings qt6-serialport: QtSerialPort bindings qt6-speech: QtTextToSpeech bindings qt6-webchannel: QtWebChannel bindings [pending] qt6-webengine: QtPdf bindings [pending] qt6-websockets: QtWebSockets bindings dbus-python: for python-dbus mainloop support [pending] installing alsa-topology-conf... installing alsa-ucm-conf... installing alsa-lib... installing aom... installing libxrender... installing lzo... installing pixman... installing cairo... installing dav1d... Optional dependencies for dav1d dav1d-doc: HTML documentation installing fribidi... installing gsm... installing libsamplerate... installing opus... installing jack2... Optional dependencies for jack2 a2jmidid: for ALSA MIDI to JACK MIDI bridging libffado: for firewire support using FFADO jack-example-tools: for official JACK example-clients and tools jack2-dbus: for dbus integration jack2-docs: for developer documentation realtime-privileges: for realtime privileges installing lame... installing libunibreak... installing libass... installing libraw1394... installing libavc1394... installing libbluray... Optional dependencies for libbluray java-runtime: BD-J library installing libogg... installing flac... installing libvorbis... installing mpg123... Optional dependencies for mpg123 sdl2: for sdl audio support [pending] jack: for jack audio support [installed] libpulse: for pulse audio support [pending] perl: for conplay [installed] installing libsndfile... Optional dependencies for libsndfile alsa-lib: for sndfile-play [installed] installing libbs2b... installing libdvdread... Optional dependencies for libdvdread libdvdcss: Decoding encrypted DVDs installing libdvdnav... installing libiec61883... installing giflib... installing libunwind... installing gperftools... Optional dependencies for gperftools graphviz: pprof graph generation perl: pprof and pprof-symbolize commands [installed] installing highway... installing imath... Optional dependencies for imath boost-libs: python bindings python: python bindings [installed] installing libdeflate... installing openexr... installing libjxl... Optional dependencies for libjxl gdk-pixbuf2: for gdk-pixbuf loader [pending] gimp: for gimp plugin java-runtime: for JNI bindings installing libmodplug... installing libasyncns... installing libpulse... Optional dependencies for libpulse glib2: mainloop integration [installed] pulse-native-provider: PulseAudio backend installing portaudio... installing libopenmpt... installing vulkan-icd-loader... Optional dependencies for vulkan-icd-loader vulkan-driver: packaged vulkan driver installing spirv-tools... installing glslang... installing jbigkit... installing libtiff... Optional dependencies for libtiff freeglut: for using tiffgt installing lcms2... installing shaderc... installing libdovi... installing xxhash... installing libplacebo... 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 [installed] librsvg: Load .svg, .svgz, and .svg.gz [pending] webp-pixbuf-loader: Load .webp installing libdatrie... installing libthai... installing libxft... installing pango... installing librsvg... installing libsoxr... installing libssh... installing libtheora... 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 libvdpau... Optional dependencies for libvdpau libvdpau-va-gl: driver using VAAPI mesa-vdpau: driver for Mesa nvidia-utils: driver for NVIDIA installing libvpx... installing libwebp... installing libxv... installing mbedtls2... installing ocl-icd... Optional dependencies for ocl-icd opencl-driver: packaged opencl driver installing libvpl... Optional dependencies for libvpl intel-media-sdk: runtime implementation for legacy Intel GPUs vpl-gpu-rt: runtime implementation for Tiger Lake and newer GPUs installing opencore-amr... installing openjpeg2... installing rav1e... installing fftw... Optional dependencies for fftw fftw-openmpi: for OpenMPI integration installing rubberband... installing libxcursor... installing hidapi... Optional dependencies for hidapi libusb: for hidapi-libusb [installed] installing sdl2... Optional dependencies for sdl2 alsa-lib: ALSA audio driver [installed] libpulse: PulseAudio audio driver [installed] jack: JACK audio driver [installed] pipewire: PipeWire audio driver libdecor: Wayland client decorations installing snappy... installing speexdsp... installing speex... installing srt... installing svt-av1... installing hicolor-icon-theme... installing v4l-utils... Optional dependencies for v4l-utils qt5-base: for qv4l2 and qvidcap alsa-lib: for qv4l2 [installed] installing zimg... installing vapoursynth... installing vid.stab... installing vmaf... installing l-smash... installing x264... installing x265... installing xvidcore... installing ffmpeg... Optional dependencies for ffmpeg avisynthplus: AviSynthPlus support frei0r-plugins: Frei0r video effects support intel-media-sdk: Intel QuickSync support (legacy) ladspa: LADSPA filters nvidia-utils: Nvidia NVDEC/NVENC support onevpl-intel-gpu: Intel QuickSync support installing libxcomposite... installing libxkbfile... installing libxdamage... installing libxrandr... installing libxslt... Optional dependencies for libxslt python: Python bindings [installed] installing libxi... installing libxtst... installing minizip... installing nspr... installing nss... installing qt6-declarative... Optional dependencies for qt6-declarative qt6-languageserver: for qmlls installing qt6-positioning... Optional dependencies for qt6-positioning geoclue: geoclue2 plugin qt6-declarative: QML bindings [installed] qt6-serialport: NMEA plugin installing qt6-webchannel... installing gnu-free-fonts... installing qt6-webengine... Optional dependencies for qt6-webengine pipewire: WebRTC desktop sharing under Wayland installing python-pyqt6-webengine... installing python-dbus... Optional dependencies for python-dbus python-gobject: D-Bus services via PyGI installing qt6-wayland... 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-annotated-types... installing python-pydantic-core... installing python-pydantic... Optional dependencies for python-pydantic mypy: for type validation with mypy python-dotenv: for .env file support python-email-validator: for email validation python-hypothesis: for hypothesis plugin when using legacy v1 installing perl-error... installing perl-timedate... installing perl-mailtools... installing git... Optional dependencies for git tk: gitk and git gui openssh: ssh transport and crypto perl-libwww: git svn perl-term-readkey: git svn and interactive.singlekey setting perl-io-socket-ssl: git send-email TLS support perl-authen-sasl: git send-email TLS support perl-mediawiki-api: git mediawiki support perl-datetime-format-iso8601: git mediawiki support perl-lwp-protocol-https: git mediawiki https support perl-cgi: gitweb (web interface) support python: git svn & git p4 [installed] subversion: git svn org.freedesktop.secrets: keyring credential helper libsecret: libsecret credential helper [installed] 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-ordered-set... installing python-platformdirs... installing python-tomli... installing python-fastjsonschema... installing python-trove-classifiers... installing python-validate-pyproject... installing python-setuptools... installing python-wheel... Optional dependencies for python-wheel python-keyring: for wheel.signatures python-xdg: for wheel.signatures installing desktop-file-utils... :: 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. Creating group 'git' with GID 972. Creating user 'git' (git daemon user) with UID 972 and GID 972. ( 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) Updating udev hardware database... ( 5/14) Reloading device manager configuration... Skipped: Device manager is not running. ( 6/14) Arming ConditionNeedsUpdate... ( 7/14) Updating the MIME type database... ( 8/14) Updating fontconfig configuration... ( 9/14) Reloading system bus configuration... Skipped: Current root is not booted. (10/14) Warn about old perl modules (11/14) Updating fontconfig cache... (12/14) Probing GDK-Pixbuf loader modules... (13/14) Updating the info directory file... (14/14) Updating the desktop file MIME type cache... ==> Making package: zapzap 5.3.6-1 (Sat 13 Jul 2024 05:28:19 AM -03) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Cloning zapzap git repo... Cloning into bare repository '/home/main-builder/pkgsrc/zapzap'... ==> WARNING: Skipping verification of source file PGP signatures. ==> Validating source files with b2sums... zapzap ... Passed ==> Extracting sources... -> Creating working copy of zapzap git repo... Cloning into 'zapzap'... done. Switched to a new branch 'makepkg' ==> Starting build()... * Getting build dependencies for wheel... * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/zapzap copying zapzap/__main__.py -> build/lib/zapzap copying zapzap/__init__.py -> build/lib/zapzap creating build/lib/zapzap/controllers copying zapzap/controllers/user_container.py -> build/lib/zapzap/controllers copying zapzap/controllers/settings.py -> build/lib/zapzap/controllers copying zapzap/controllers/qtoaster_donation.py -> build/lib/zapzap/controllers copying zapzap/controllers/open_chat_popup.py -> build/lib/zapzap/controllers copying zapzap/controllers/main_window.py -> build/lib/zapzap/controllers copying zapzap/controllers/home.py -> build/lib/zapzap/controllers copying zapzap/controllers/drawer.py -> build/lib/zapzap/controllers copying zapzap/controllers/download_popup.py -> build/lib/zapzap/controllers copying zapzap/controllers/card_user.py -> build/lib/zapzap/controllers copying zapzap/controllers/SingleApplication.py -> build/lib/zapzap/controllers creating build/lib/zapzap/controllers/main_window_components copying zapzap/controllers/main_window_components/tray_icon.py -> build/lib/zapzap/controllers/main_window_components copying zapzap/controllers/main_window_components/builder_icon.py -> build/lib/zapzap/controllers/main_window_components creating build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/tools.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/personalization.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/notifications.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/network.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/general.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/donations.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/advanced.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/account.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/about.py -> build/lib/zapzap/controllers/settings_pages creating build/lib/zapzap/engine copying zapzap/engine/whatsapp.py -> build/lib/zapzap/engine copying zapzap/engine/browser.py -> build/lib/zapzap/engine creating build/lib/zapzap/services copying zapzap/services/spellCheckLanguages.py -> build/lib/zapzap/services copying zapzap/services/qtoaster.py -> build/lib/zapzap/services copying zapzap/services/portal_desktop.py -> build/lib/zapzap/services copying zapzap/services/dbus_theme.py -> build/lib/zapzap/services copying zapzap/services/dbus_notify.py -> build/lib/zapzap/services creating build/lib/zapzap/theme copying zapzap/theme/zap_themes.py -> build/lib/zapzap/theme copying zapzap/theme/style.py -> build/lib/zapzap/theme copying zapzap/theme/icons.py -> build/lib/zapzap/theme copying zapzap/theme/builder_icon.py -> build/lib/zapzap/theme creating build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/settings.py -> build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/qwidgets.py -> build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/popup.py -> build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/menu_home.py -> build/lib/zapzap/theme/style_components creating build/lib/zapzap/view copying zapzap/view/settings.py -> build/lib/zapzap/view copying zapzap/view/qtoaster_donation.py -> build/lib/zapzap/view copying zapzap/view/personalization_page.py -> build/lib/zapzap/view copying zapzap/view/openChatPopup.py -> build/lib/zapzap/view copying zapzap/view/notifications_page.py -> build/lib/zapzap/view copying zapzap/view/network_page.py -> build/lib/zapzap/view copying zapzap/view/main_window.py -> build/lib/zapzap/view copying zapzap/view/home.py -> build/lib/zapzap/view copying zapzap/view/general_page.py -> build/lib/zapzap/view copying zapzap/view/drawer.py -> build/lib/zapzap/view copying zapzap/view/downloadPopup.py -> build/lib/zapzap/view copying zapzap/view/donations_page.py -> build/lib/zapzap/view copying zapzap/view/card_user.py -> build/lib/zapzap/view copying zapzap/view/advanced_page.py -> build/lib/zapzap/view copying zapzap/view/account_page.py -> build/lib/zapzap/view copying zapzap/view/about_page.py -> build/lib/zapzap/view creating build/lib/zapzap/model copying zapzap/model/user.py -> build/lib/zapzap/model copying zapzap/model/db.py -> build/lib/zapzap/model running egg_info creating zapzap.egg-info writing zapzap.egg-info/PKG-INFO writing dependency_links to zapzap.egg-info/dependency_links.txt writing entry points to zapzap.egg-info/entry_points.txt writing top-level names to zapzap.egg-info/top_level.txt writing manifest file 'zapzap.egg-info/SOURCES.txt' reading manifest file 'zapzap.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'zapzap.egg-info/SOURCES.txt' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.assets.icons.app.dark' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.app.dark' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.app.dark' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.app.dark' to be distributed and are already explicitly excluding 'zapzap.assets.icons.app.dark' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.assets.icons.app.light' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.app.light' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.app.light' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.app.light' to be distributed and are already explicitly excluding 'zapzap.assets.icons.app.light' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.assets.icons.banners' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.banners' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.banners' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.banners' to be distributed and are already explicitly excluding 'zapzap.assets.icons.banners' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.assets.icons.titlebar_buttons.default.dark' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.titlebar_buttons.default.dark' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.titlebar_buttons.default.dark' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.titlebar_buttons.default.dark' to be distributed and are already explicitly excluding 'zapzap.assets.icons.titlebar_buttons.default.dark' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.assets.icons.titlebar_buttons.default.light' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.titlebar_buttons.default.light' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.titlebar_buttons.default.light' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.titlebar_buttons.default.light' to be distributed and are already explicitly excluding 'zapzap.assets.icons.titlebar_buttons.default.light' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.assets.icons.tray' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.tray' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.tray' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.tray' to be distributed and are already explicitly excluding 'zapzap.assets.icons.tray' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.am.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.am.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.am.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.am.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.am.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.kmr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.kmr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.kmr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.kmr.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.kmr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.nb_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.nb_NO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.nb_NO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.nb_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.nb_NO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.oc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.oc.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.oc.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.oc.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.oc.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.si.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.si.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.si.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.si.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.si.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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 'zapzap.po.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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 'zapzap.po.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.po.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.po.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'zapzap.po.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.po.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 'zapzap.po.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 'zapzap.po.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'zapzap.po.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) creating build/lib/zapzap/assets creating build/lib/zapzap/assets/icons creating build/lib/zapzap/assets/icons/app creating build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/about.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/appearance.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/bell-ringing.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/bell-slash.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/border.png -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/borderDialog.png -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/chat.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_checked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_checked_disabled.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_indeterminate.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_indeterminate_disabled.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_unchecked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_unchecked_disabled.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/donations.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/expand_more.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/eye-slash.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/eye.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/gear-six.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/manage_accounts.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/network.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/notifications.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/phone-plus.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/sign-out.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/system.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/transparent.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/trash.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/user-plus.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/user.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/wrench.svg -> build/lib/zapzap/assets/icons/app/dark creating build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/about.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/appearance.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/bell-ringing.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/bell-slash.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/border.png -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/borderDialog.png -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/chat.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_checked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_checked_disabled.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_indeterminate.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_indeterminate_disabled.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_unchecked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_unchecked_disabled.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/donations.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/expand_more.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/eye-slash.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/eye.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/gear-six.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/manage_accounts.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/network.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/notifications.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/phone-plus.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/sign-out.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/system.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/transparent.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/trash.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/user-plus.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/user.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/wrench.svg -> build/lib/zapzap/assets/icons/app/light creating build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/PayPal.png -> build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/kofi.svg -> build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/pix.png -> build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/sponsor.svg -> build/lib/zapzap/assets/icons/banners creating build/lib/zapzap/assets/icons/titlebar_buttons creating build/lib/zapzap/assets/icons/titlebar_buttons/default creating build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_close.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark creating build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_close.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light creating build/lib/zapzap/assets/icons/tray copying zapzap/assets/icons/tray/default_normal.svg -> build/lib/zapzap/assets/icons/tray copying zapzap/assets/icons/tray/model.svg -> build/lib/zapzap/assets/icons/tray copying zapzap/assets/icons/tray/simbolic_model.svg -> build/lib/zapzap/assets/icons/tray creating build/lib/zapzap/po creating build/lib/zapzap/po/am creating build/lib/zapzap/po/am/LC_MESSAGES copying zapzap/po/am/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/am/LC_MESSAGES creating build/lib/zapzap/po/ar creating build/lib/zapzap/po/ar/LC_MESSAGES copying zapzap/po/ar/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ar/LC_MESSAGES creating build/lib/zapzap/po/ca creating build/lib/zapzap/po/ca/LC_MESSAGES copying zapzap/po/ca/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ca/LC_MESSAGES creating build/lib/zapzap/po/cs creating build/lib/zapzap/po/cs/LC_MESSAGES copying zapzap/po/cs/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/cs/LC_MESSAGES creating build/lib/zapzap/po/da creating build/lib/zapzap/po/da/LC_MESSAGES copying zapzap/po/da/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/da/LC_MESSAGES creating build/lib/zapzap/po/de creating build/lib/zapzap/po/de/LC_MESSAGES copying zapzap/po/de/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/de/LC_MESSAGES creating build/lib/zapzap/po/el creating build/lib/zapzap/po/el/LC_MESSAGES copying zapzap/po/el/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/el/LC_MESSAGES creating build/lib/zapzap/po/eo creating build/lib/zapzap/po/eo/LC_MESSAGES copying zapzap/po/eo/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/eo/LC_MESSAGES creating build/lib/zapzap/po/es creating build/lib/zapzap/po/es/LC_MESSAGES copying zapzap/po/es/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/es/LC_MESSAGES creating build/lib/zapzap/po/eu creating build/lib/zapzap/po/eu/LC_MESSAGES copying zapzap/po/eu/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/eu/LC_MESSAGES creating build/lib/zapzap/po/fa creating build/lib/zapzap/po/fa/LC_MESSAGES copying zapzap/po/fa/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fa/LC_MESSAGES creating build/lib/zapzap/po/fi creating build/lib/zapzap/po/fi/LC_MESSAGES copying zapzap/po/fi/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fi/LC_MESSAGES creating build/lib/zapzap/po/fr creating build/lib/zapzap/po/fr/LC_MESSAGES copying zapzap/po/fr/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fr/LC_MESSAGES creating build/lib/zapzap/po/fy creating build/lib/zapzap/po/fy/LC_MESSAGES copying zapzap/po/fy/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fy/LC_MESSAGES creating build/lib/zapzap/po/gl creating build/lib/zapzap/po/gl/LC_MESSAGES copying zapzap/po/gl/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/gl/LC_MESSAGES creating build/lib/zapzap/po/he creating build/lib/zapzap/po/he/LC_MESSAGES copying zapzap/po/he/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/he/LC_MESSAGES creating build/lib/zapzap/po/hi creating build/lib/zapzap/po/hi/LC_MESSAGES copying zapzap/po/hi/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/hi/LC_MESSAGES creating build/lib/zapzap/po/hr creating build/lib/zapzap/po/hr/LC_MESSAGES copying zapzap/po/hr/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/hr/LC_MESSAGES creating build/lib/zapzap/po/hu creating build/lib/zapzap/po/hu/LC_MESSAGES copying zapzap/po/hu/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/hu/LC_MESSAGES creating build/lib/zapzap/po/id creating build/lib/zapzap/po/id/LC_MESSAGES copying zapzap/po/id/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/id/LC_MESSAGES creating build/lib/zapzap/po/it creating build/lib/zapzap/po/it/LC_MESSAGES copying zapzap/po/it/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/it/LC_MESSAGES creating build/lib/zapzap/po/ja creating build/lib/zapzap/po/ja/LC_MESSAGES copying zapzap/po/ja/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ja/LC_MESSAGES creating build/lib/zapzap/po/ka creating build/lib/zapzap/po/ka/LC_MESSAGES copying zapzap/po/ka/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ka/LC_MESSAGES creating build/lib/zapzap/po/kmr creating build/lib/zapzap/po/kmr/LC_MESSAGES copying zapzap/po/kmr/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/kmr/LC_MESSAGES creating build/lib/zapzap/po/kn creating build/lib/zapzap/po/kn/LC_MESSAGES copying zapzap/po/kn/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/kn/LC_MESSAGES creating build/lib/zapzap/po/ko creating build/lib/zapzap/po/ko/LC_MESSAGES copying zapzap/po/ko/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ko/LC_MESSAGES creating build/lib/zapzap/po/lt creating build/lib/zapzap/po/lt/LC_MESSAGES copying zapzap/po/lt/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/lt/LC_MESSAGES creating build/lib/zapzap/po/lv creating build/lib/zapzap/po/lv/LC_MESSAGES copying zapzap/po/lv/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/lv/LC_MESSAGES creating build/lib/zapzap/po/nb_NO creating build/lib/zapzap/po/nb_NO/LC_MESSAGES copying zapzap/po/nb_NO/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/nb_NO/LC_MESSAGES creating build/lib/zapzap/po/nl creating build/lib/zapzap/po/nl/LC_MESSAGES copying zapzap/po/nl/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/nl/LC_MESSAGES creating build/lib/zapzap/po/oc creating build/lib/zapzap/po/oc/LC_MESSAGES copying zapzap/po/oc/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/oc/LC_MESSAGES creating build/lib/zapzap/po/pl creating build/lib/zapzap/po/pl/LC_MESSAGES copying zapzap/po/pl/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/pl/LC_MESSAGES creating build/lib/zapzap/po/pt creating build/lib/zapzap/po/pt/LC_MESSAGES copying zapzap/po/pt/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/pt/LC_MESSAGES creating build/lib/zapzap/po/pt_BR creating build/lib/zapzap/po/pt_BR/LC_MESSAGES copying zapzap/po/pt_BR/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/pt_BR/LC_MESSAGES creating build/lib/zapzap/po/ru creating build/lib/zapzap/po/ru/LC_MESSAGES copying zapzap/po/ru/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ru/LC_MESSAGES creating build/lib/zapzap/po/si creating build/lib/zapzap/po/si/LC_MESSAGES copying zapzap/po/si/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/si/LC_MESSAGES creating build/lib/zapzap/po/sk creating build/lib/zapzap/po/sk/LC_MESSAGES copying zapzap/po/sk/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/sk/LC_MESSAGES creating build/lib/zapzap/po/sr creating build/lib/zapzap/po/sr/LC_MESSAGES copying zapzap/po/sr/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/sr/LC_MESSAGES creating build/lib/zapzap/po/sv creating build/lib/zapzap/po/sv/LC_MESSAGES copying zapzap/po/sv/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/sv/LC_MESSAGES creating build/lib/zapzap/po/tr creating build/lib/zapzap/po/tr/LC_MESSAGES copying zapzap/po/tr/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/tr/LC_MESSAGES creating build/lib/zapzap/po/uk creating build/lib/zapzap/po/uk/LC_MESSAGES copying zapzap/po/uk/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/uk/LC_MESSAGES creating build/lib/zapzap/po/zh_CN creating build/lib/zapzap/po/zh_CN/LC_MESSAGES copying zapzap/po/zh_CN/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/zh_CN/LC_MESSAGES installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/zapzap creating build/bdist.linux-x86_64/wheel/zapzap/po creating build/bdist.linux-x86_64/wheel/zapzap/po/zh_CN creating build/bdist.linux-x86_64/wheel/zapzap/po/zh_CN/LC_MESSAGES copying build/lib/zapzap/po/zh_CN/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/zh_CN/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/uk creating build/bdist.linux-x86_64/wheel/zapzap/po/uk/LC_MESSAGES copying build/lib/zapzap/po/uk/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/tr creating build/bdist.linux-x86_64/wheel/zapzap/po/tr/LC_MESSAGES copying build/lib/zapzap/po/tr/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/sv creating build/bdist.linux-x86_64/wheel/zapzap/po/sv/LC_MESSAGES copying build/lib/zapzap/po/sv/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/sr creating build/bdist.linux-x86_64/wheel/zapzap/po/sr/LC_MESSAGES copying build/lib/zapzap/po/sr/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/sk creating build/bdist.linux-x86_64/wheel/zapzap/po/sk/LC_MESSAGES copying build/lib/zapzap/po/sk/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/si creating build/bdist.linux-x86_64/wheel/zapzap/po/si/LC_MESSAGES copying build/lib/zapzap/po/si/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/si/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/ru creating build/bdist.linux-x86_64/wheel/zapzap/po/ru/LC_MESSAGES copying build/lib/zapzap/po/ru/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/pt_BR creating build/bdist.linux-x86_64/wheel/zapzap/po/pt_BR/LC_MESSAGES copying build/lib/zapzap/po/pt_BR/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/pt creating build/bdist.linux-x86_64/wheel/zapzap/po/pt/LC_MESSAGES copying build/lib/zapzap/po/pt/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/pl creating build/bdist.linux-x86_64/wheel/zapzap/po/pl/LC_MESSAGES copying build/lib/zapzap/po/pl/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/oc creating build/bdist.linux-x86_64/wheel/zapzap/po/oc/LC_MESSAGES copying build/lib/zapzap/po/oc/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/oc/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/nl creating build/bdist.linux-x86_64/wheel/zapzap/po/nl/LC_MESSAGES copying build/lib/zapzap/po/nl/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/nb_NO creating build/bdist.linux-x86_64/wheel/zapzap/po/nb_NO/LC_MESSAGES copying build/lib/zapzap/po/nb_NO/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/nb_NO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/lv creating build/bdist.linux-x86_64/wheel/zapzap/po/lv/LC_MESSAGES copying build/lib/zapzap/po/lv/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/lt creating build/bdist.linux-x86_64/wheel/zapzap/po/lt/LC_MESSAGES copying build/lib/zapzap/po/lt/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/ko creating build/bdist.linux-x86_64/wheel/zapzap/po/ko/LC_MESSAGES copying build/lib/zapzap/po/ko/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/kn creating build/bdist.linux-x86_64/wheel/zapzap/po/kn/LC_MESSAGES copying build/lib/zapzap/po/kn/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/kmr creating build/bdist.linux-x86_64/wheel/zapzap/po/kmr/LC_MESSAGES copying build/lib/zapzap/po/kmr/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/kmr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/ka creating build/bdist.linux-x86_64/wheel/zapzap/po/ka/LC_MESSAGES copying build/lib/zapzap/po/ka/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/ja creating build/bdist.linux-x86_64/wheel/zapzap/po/ja/LC_MESSAGES copying build/lib/zapzap/po/ja/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/it creating build/bdist.linux-x86_64/wheel/zapzap/po/it/LC_MESSAGES copying build/lib/zapzap/po/it/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/id creating build/bdist.linux-x86_64/wheel/zapzap/po/id/LC_MESSAGES copying build/lib/zapzap/po/id/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/hu creating build/bdist.linux-x86_64/wheel/zapzap/po/hu/LC_MESSAGES copying build/lib/zapzap/po/hu/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/hr creating build/bdist.linux-x86_64/wheel/zapzap/po/hr/LC_MESSAGES copying build/lib/zapzap/po/hr/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/hi creating build/bdist.linux-x86_64/wheel/zapzap/po/hi/LC_MESSAGES copying build/lib/zapzap/po/hi/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/he creating build/bdist.linux-x86_64/wheel/zapzap/po/he/LC_MESSAGES copying build/lib/zapzap/po/he/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/gl creating build/bdist.linux-x86_64/wheel/zapzap/po/gl/LC_MESSAGES copying build/lib/zapzap/po/gl/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/fy creating build/bdist.linux-x86_64/wheel/zapzap/po/fy/LC_MESSAGES copying build/lib/zapzap/po/fy/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/fr creating build/bdist.linux-x86_64/wheel/zapzap/po/fr/LC_MESSAGES copying build/lib/zapzap/po/fr/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/fi creating build/bdist.linux-x86_64/wheel/zapzap/po/fi/LC_MESSAGES copying build/lib/zapzap/po/fi/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/fa creating build/bdist.linux-x86_64/wheel/zapzap/po/fa/LC_MESSAGES copying build/lib/zapzap/po/fa/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/eu creating build/bdist.linux-x86_64/wheel/zapzap/po/eu/LC_MESSAGES copying build/lib/zapzap/po/eu/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/es creating build/bdist.linux-x86_64/wheel/zapzap/po/es/LC_MESSAGES copying build/lib/zapzap/po/es/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/eo creating build/bdist.linux-x86_64/wheel/zapzap/po/eo/LC_MESSAGES copying build/lib/zapzap/po/eo/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/el creating build/bdist.linux-x86_64/wheel/zapzap/po/el/LC_MESSAGES copying build/lib/zapzap/po/el/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/de creating build/bdist.linux-x86_64/wheel/zapzap/po/de/LC_MESSAGES copying build/lib/zapzap/po/de/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/da creating build/bdist.linux-x86_64/wheel/zapzap/po/da/LC_MESSAGES copying build/lib/zapzap/po/da/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/cs creating build/bdist.linux-x86_64/wheel/zapzap/po/cs/LC_MESSAGES copying build/lib/zapzap/po/cs/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/ca creating build/bdist.linux-x86_64/wheel/zapzap/po/ca/LC_MESSAGES copying build/lib/zapzap/po/ca/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/ar creating build/bdist.linux-x86_64/wheel/zapzap/po/ar/LC_MESSAGES copying build/lib/zapzap/po/ar/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/po/am creating build/bdist.linux-x86_64/wheel/zapzap/po/am/LC_MESSAGES copying build/lib/zapzap/po/am/LC_MESSAGES/zapzap.mo -> build/bdist.linux-x86_64/wheel/zapzap/po/am/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/zapzap/assets creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/tray copying build/lib/zapzap/assets/icons/tray/simbolic_model.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/tray copying build/lib/zapzap/assets/icons/tray/model.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/tray copying build/lib/zapzap/assets/icons/tray/default_normal.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/tray creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/titlebar_buttons creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/titlebar_buttons/default creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_close.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/titlebar_buttons/default/light creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_close.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/titlebar_buttons/default/dark creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/sponsor.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/pix.png -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/kofi.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/PayPal.png -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/banners creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/wrench.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/user.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/user-plus.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/trash.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/transparent.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/system.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/sign-out.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/phone-plus.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/notifications.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/network.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/manage_accounts.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/gear-six.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/eye.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/eye-slash.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/expand_more.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/donations.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_unchecked_disabled.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_unchecked.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_indeterminate_disabled.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_indeterminate.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_checked_disabled.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_checked.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/chat.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/borderDialog.png -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/border.png -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/bell-slash.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/bell-ringing.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/appearance.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/about.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/light creating build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/wrench.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/user.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/user-plus.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/trash.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/transparent.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/system.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/sign-out.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/phone-plus.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/notifications.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/network.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/manage_accounts.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/gear-six.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/eye.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/eye-slash.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/expand_more.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/donations.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_unchecked_disabled.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_unchecked.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_indeterminate_disabled.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_indeterminate.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_checked_disabled.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_checked.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/chat.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/borderDialog.png -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/border.png -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/bell-slash.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/bell-ringing.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/appearance.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/about.svg -> build/bdist.linux-x86_64/wheel/zapzap/assets/icons/app/dark creating build/bdist.linux-x86_64/wheel/zapzap/model copying build/lib/zapzap/model/db.py -> build/bdist.linux-x86_64/wheel/zapzap/model copying build/lib/zapzap/model/user.py -> build/bdist.linux-x86_64/wheel/zapzap/model creating build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/about_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/account_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/advanced_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/card_user.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/donations_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/downloadPopup.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/drawer.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/general_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/home.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/main_window.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/network_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/notifications_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/openChatPopup.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/personalization_page.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/qtoaster_donation.py -> build/bdist.linux-x86_64/wheel/zapzap/view copying build/lib/zapzap/view/settings.py -> build/bdist.linux-x86_64/wheel/zapzap/view creating build/bdist.linux-x86_64/wheel/zapzap/theme creating build/bdist.linux-x86_64/wheel/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/menu_home.py -> build/bdist.linux-x86_64/wheel/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/popup.py -> build/bdist.linux-x86_64/wheel/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/qwidgets.py -> build/bdist.linux-x86_64/wheel/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/settings.py -> build/bdist.linux-x86_64/wheel/zapzap/theme/style_components copying build/lib/zapzap/theme/builder_icon.py -> build/bdist.linux-x86_64/wheel/zapzap/theme copying build/lib/zapzap/theme/icons.py -> build/bdist.linux-x86_64/wheel/zapzap/theme copying build/lib/zapzap/theme/style.py -> build/bdist.linux-x86_64/wheel/zapzap/theme copying build/lib/zapzap/theme/zap_themes.py -> build/bdist.linux-x86_64/wheel/zapzap/theme creating build/bdist.linux-x86_64/wheel/zapzap/services copying build/lib/zapzap/services/dbus_notify.py -> build/bdist.linux-x86_64/wheel/zapzap/services copying build/lib/zapzap/services/dbus_theme.py -> build/bdist.linux-x86_64/wheel/zapzap/services copying build/lib/zapzap/services/portal_desktop.py -> build/bdist.linux-x86_64/wheel/zapzap/services copying build/lib/zapzap/services/qtoaster.py -> build/bdist.linux-x86_64/wheel/zapzap/services copying build/lib/zapzap/services/spellCheckLanguages.py -> build/bdist.linux-x86_64/wheel/zapzap/services creating build/bdist.linux-x86_64/wheel/zapzap/engine copying build/lib/zapzap/engine/browser.py -> build/bdist.linux-x86_64/wheel/zapzap/engine copying build/lib/zapzap/engine/whatsapp.py -> build/bdist.linux-x86_64/wheel/zapzap/engine creating build/bdist.linux-x86_64/wheel/zapzap/controllers creating build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/about.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/account.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/advanced.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/donations.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/general.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/network.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/notifications.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/personalization.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/tools.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/settings_pages creating build/bdist.linux-x86_64/wheel/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/builder_icon.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/tray_icon.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/SingleApplication.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/card_user.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/download_popup.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/drawer.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/home.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/main_window.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/open_chat_popup.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/qtoaster_donation.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/settings.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/controllers/user_container.py -> build/bdist.linux-x86_64/wheel/zapzap/controllers copying build/lib/zapzap/__init__.py -> build/bdist.linux-x86_64/wheel/zapzap copying build/lib/zapzap/__main__.py -> build/bdist.linux-x86_64/wheel/zapzap running install_egg_info Copying zapzap.egg-info to build/bdist.linux-x86_64/wheel/zapzap-5.3-py3.12.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/zapzap-5.3.dist-info/WHEEL creating '/home/main-builder/pkgwork/src/zapzap/dist/.tmp-dazvau9e/zapzap-5.3-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'zapzap/__init__.py' adding 'zapzap/__main__.py' adding 'zapzap/assets/icons/app/dark/about.svg' adding 'zapzap/assets/icons/app/dark/appearance.svg' adding 'zapzap/assets/icons/app/dark/bell-ringing.svg' adding 'zapzap/assets/icons/app/dark/bell-slash.svg' adding 'zapzap/assets/icons/app/dark/border.png' adding 'zapzap/assets/icons/app/dark/borderDialog.png' adding 'zapzap/assets/icons/app/dark/chat.svg' adding 'zapzap/assets/icons/app/dark/checkbox_checked.svg' adding 'zapzap/assets/icons/app/dark/checkbox_checked_disabled.svg' adding 'zapzap/assets/icons/app/dark/checkbox_indeterminate.svg' adding 'zapzap/assets/icons/app/dark/checkbox_indeterminate_disabled.svg' adding 'zapzap/assets/icons/app/dark/checkbox_unchecked.svg' adding 'zapzap/assets/icons/app/dark/checkbox_unchecked_disabled.svg' adding 'zapzap/assets/icons/app/dark/donations.svg' adding 'zapzap/assets/icons/app/dark/expand_more.svg' adding 'zapzap/assets/icons/app/dark/eye-slash.svg' adding 'zapzap/assets/icons/app/dark/eye.svg' adding 'zapzap/assets/icons/app/dark/gear-six.svg' adding 'zapzap/assets/icons/app/dark/manage_accounts.svg' adding 'zapzap/assets/icons/app/dark/network.svg' adding 'zapzap/assets/icons/app/dark/notifications.svg' adding 'zapzap/assets/icons/app/dark/phone-plus.svg' adding 'zapzap/assets/icons/app/dark/sign-out.svg' adding 'zapzap/assets/icons/app/dark/system.svg' adding 'zapzap/assets/icons/app/dark/transparent.svg' adding 'zapzap/assets/icons/app/dark/trash.svg' adding 'zapzap/assets/icons/app/dark/user-plus.svg' adding 'zapzap/assets/icons/app/dark/user.svg' adding 'zapzap/assets/icons/app/dark/wrench.svg' adding 'zapzap/assets/icons/app/light/about.svg' adding 'zapzap/assets/icons/app/light/appearance.svg' adding 'zapzap/assets/icons/app/light/bell-ringing.svg' adding 'zapzap/assets/icons/app/light/bell-slash.svg' adding 'zapzap/assets/icons/app/light/border.png' adding 'zapzap/assets/icons/app/light/borderDialog.png' adding 'zapzap/assets/icons/app/light/chat.svg' adding 'zapzap/assets/icons/app/light/checkbox_checked.svg' adding 'zapzap/assets/icons/app/light/checkbox_checked_disabled.svg' adding 'zapzap/assets/icons/app/light/checkbox_indeterminate.svg' adding 'zapzap/assets/icons/app/light/checkbox_indeterminate_disabled.svg' adding 'zapzap/assets/icons/app/light/checkbox_unchecked.svg' adding 'zapzap/assets/icons/app/light/checkbox_unchecked_disabled.svg' adding 'zapzap/assets/icons/app/light/donations.svg' adding 'zapzap/assets/icons/app/light/expand_more.svg' adding 'zapzap/assets/icons/app/light/eye-slash.svg' adding 'zapzap/assets/icons/app/light/eye.svg' adding 'zapzap/assets/icons/app/light/gear-six.svg' adding 'zapzap/assets/icons/app/light/manage_accounts.svg' adding 'zapzap/assets/icons/app/light/network.svg' adding 'zapzap/assets/icons/app/light/notifications.svg' adding 'zapzap/assets/icons/app/light/phone-plus.svg' adding 'zapzap/assets/icons/app/light/sign-out.svg' adding 'zapzap/assets/icons/app/light/system.svg' adding 'zapzap/assets/icons/app/light/transparent.svg' adding 'zapzap/assets/icons/app/light/trash.svg' adding 'zapzap/assets/icons/app/light/user-plus.svg' adding 'zapzap/assets/icons/app/light/user.svg' adding 'zapzap/assets/icons/app/light/wrench.svg' adding 'zapzap/assets/icons/banners/PayPal.png' adding 'zapzap/assets/icons/banners/kofi.svg' adding 'zapzap/assets/icons/banners/pix.png' adding 'zapzap/assets/icons/banners/sponsor.svg' adding 'zapzap/assets/icons/titlebar_buttons/default/dark/btn_close.svg' adding 'zapzap/assets/icons/titlebar_buttons/default/light/btn_close.svg' adding 'zapzap/assets/icons/tray/default_normal.svg' adding 'zapzap/assets/icons/tray/model.svg' adding 'zapzap/assets/icons/tray/simbolic_model.svg' adding 'zapzap/controllers/SingleApplication.py' adding 'zapzap/controllers/card_user.py' adding 'zapzap/controllers/download_popup.py' adding 'zapzap/controllers/drawer.py' adding 'zapzap/controllers/home.py' adding 'zapzap/controllers/main_window.py' adding 'zapzap/controllers/open_chat_popup.py' adding 'zapzap/controllers/qtoaster_donation.py' adding 'zapzap/controllers/settings.py' adding 'zapzap/controllers/user_container.py' adding 'zapzap/controllers/main_window_components/builder_icon.py' adding 'zapzap/controllers/main_window_components/tray_icon.py' adding 'zapzap/controllers/settings_pages/about.py' adding 'zapzap/controllers/settings_pages/account.py' adding 'zapzap/controllers/settings_pages/advanced.py' adding 'zapzap/controllers/settings_pages/donations.py' adding 'zapzap/controllers/settings_pages/general.py' adding 'zapzap/controllers/settings_pages/network.py' adding 'zapzap/controllers/settings_pages/notifications.py' adding 'zapzap/controllers/settings_pages/personalization.py' adding 'zapzap/controllers/settings_pages/tools.py' adding 'zapzap/engine/browser.py' adding 'zapzap/engine/whatsapp.py' adding 'zapzap/model/db.py' adding 'zapzap/model/user.py' adding 'zapzap/po/am/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/ar/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/ca/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/cs/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/da/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/de/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/el/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/eo/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/es/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/eu/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/fa/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/fi/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/fr/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/fy/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/gl/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/he/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/hi/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/hr/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/hu/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/id/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/it/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/ja/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/ka/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/kmr/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/kn/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/ko/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/lt/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/lv/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/nb_NO/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/nl/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/oc/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/pl/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/pt/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/pt_BR/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/ru/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/si/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/sk/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/sr/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/sv/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/tr/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/uk/LC_MESSAGES/zapzap.mo' adding 'zapzap/po/zh_CN/LC_MESSAGES/zapzap.mo' adding 'zapzap/services/dbus_notify.py' adding 'zapzap/services/dbus_theme.py' adding 'zapzap/services/portal_desktop.py' adding 'zapzap/services/qtoaster.py' adding 'zapzap/services/spellCheckLanguages.py' adding 'zapzap/theme/builder_icon.py' adding 'zapzap/theme/icons.py' adding 'zapzap/theme/style.py' adding 'zapzap/theme/zap_themes.py' adding 'zapzap/theme/style_components/menu_home.py' adding 'zapzap/theme/style_components/popup.py' adding 'zapzap/theme/style_components/qwidgets.py' adding 'zapzap/theme/style_components/settings.py' adding 'zapzap/view/about_page.py' adding 'zapzap/view/account_page.py' adding 'zapzap/view/advanced_page.py' adding 'zapzap/view/card_user.py' adding 'zapzap/view/donations_page.py' adding 'zapzap/view/downloadPopup.py' adding 'zapzap/view/drawer.py' adding 'zapzap/view/general_page.py' adding 'zapzap/view/home.py' adding 'zapzap/view/main_window.py' adding 'zapzap/view/network_page.py' adding 'zapzap/view/notifications_page.py' adding 'zapzap/view/openChatPopup.py' adding 'zapzap/view/personalization_page.py' adding 'zapzap/view/qtoaster_donation.py' adding 'zapzap/view/settings.py' adding 'zapzap-5.3.dist-info/LICENSE' adding 'zapzap-5.3.dist-info/METADATA' adding 'zapzap-5.3.dist-info/WHEEL' adding 'zapzap-5.3.dist-info/entry_points.txt' adding 'zapzap-5.3.dist-info/top_level.txt' adding 'zapzap-5.3.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built zapzap-5.3-py3-none-any.whl ==> Entering fakeroot environment... ==> Starting package()... ==> Tidying install... -> 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 "zapzap"... -> Generating .PKGINFO file... -> Generating .BUILDINFO file... -> Generating .MTREE file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: zapzap 5.3.6-1 (Sat 13 Jul 2024 05:28:26 AM -03) real 0m28.003s user 0m12.925s sys 0m14.235s