Mock Version: 4.0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/zapzap.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1685831483.950570/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.1saf0h6z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=True) Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.1saf0h6z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '4d8063c41b0d44188be19c7475a7805b', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1685831483.950570/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.1saf0h6z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/zapzap.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1685750400 Wrote: /builddir/build/SRPMS/zapzap-4.4.6-2.fc39.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/zapzap.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1685831483.950570/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.1saf0h6z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=True) Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.1saf0h6z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '7154840cd4384cf6b8ce2b1fd9751670', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1685831483.950570/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.1saf0h6z:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/zapzap.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1685750400 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.dJ4OaU + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf zapzap-4.4.6 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/4.4.6.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd zapzap-4.4.6 + /usr/bin/mkdir -p SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.7ptVBz + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd zapzap-4.4.6 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' /usr/lib/python3.11/site-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. 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/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/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/menu_bar.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/main_window_decoration copying zapzap/controllers/main_window_decoration/ui_decoration.py -> build/lib/zapzap/controllers/main_window_decoration copying zapzap/controllers/main_window_decoration/ui_actions.py -> build/lib/zapzap/controllers/main_window_decoration copying zapzap/controllers/main_window_decoration/custom_grips.py -> build/lib/zapzap/controllers/main_window_decoration 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/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/view copying zapzap/view/settings.py -> build/lib/zapzap/view copying zapzap/view/openChatPopup.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/downloadPopup.py -> build/lib/zapzap/view copying zapzap/view/card_user.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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'zapzap.assets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets' as an importable package[^1], but it 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' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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' to be distributed and are already explicitly excluding 'zapzap.assets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package '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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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) 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/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/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/home.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/notifications.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/theme_dark_checked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/theme_dark_unchecked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/theme_light_checked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/theme_light_unchecked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/theme_system_checked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/theme_system_unchecked.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/tray_dark.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/tray_default.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/tray_light.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/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/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/home.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/modelo.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/system.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/theme_dark_checked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/theme_dark_unchecked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/theme_light_checked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/theme_light_unchecked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/theme_system_checked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/theme_system_unchecked.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/tray_dark.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/tray_default.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/tray_light.svg -> build/lib/zapzap/assets/icons/app/light creating build/lib/zapzap/assets/icons/banners /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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) 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 copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_close_hover.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_maximize.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_maximize_hover.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_minimize.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_minimize_hover.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_settings.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 copying zapzap/assets/icons/titlebar_buttons/default/light/btn_close_hover.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_maximize.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_maximize_hover.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_minimize.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_minimize_hover.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_settings.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light creating build/lib/zapzap/assets/segoe-ui copying zapzap/assets/segoe-ui/Segoe UI Bold Italic.ttf -> build/lib/zapzap/assets/segoe-ui copying zapzap/assets/segoe-ui/Segoe UI Bold.ttf -> build/lib/zapzap/assets/segoe-ui copying zapzap/assets/segoe-ui/Segoe UI Italic.ttf -> build/lib/zapzap/assets/segoe-ui copying zapzap/assets/segoe-ui/Segoe UI.ttf -> build/lib/zapzap/assets/segoe-ui 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 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.Bf2o34 + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 ++ dirname /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd zapzap-4.4.6 + /usr/bin/python3 setup.py install --root /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 /usr/lib/python3.11/site-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. running install /usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer, pypa/build or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !! self.initialize_options() running build running build_py running 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 reading manifest file 'zapzap.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'zapzap.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'zapzap.assets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets' as an importable package[^1], but it 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' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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' to be distributed and are already explicitly excluding 'zapzap.assets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package '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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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) running install_lib creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11 creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/zh_CN creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/zh_CN/LC_MESSAGES copying build/lib/zapzap/po/zh_CN/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/zh_CN/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/uk creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/uk/LC_MESSAGES copying build/lib/zapzap/po/uk/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/tr creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/tr/LC_MESSAGES copying build/lib/zapzap/po/tr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sv creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sv/LC_MESSAGES copying build/lib/zapzap/po/sv/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sr creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sr/LC_MESSAGES copying build/lib/zapzap/po/sr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sk creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sk/LC_MESSAGES copying build/lib/zapzap/po/sk/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/si creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/si/LC_MESSAGES copying build/lib/zapzap/po/si/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/si/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ru creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ru/LC_MESSAGES copying build/lib/zapzap/po/ru/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pt_BR creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pt_BR/LC_MESSAGES copying build/lib/zapzap/po/pt_BR/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pt creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pt/LC_MESSAGES copying build/lib/zapzap/po/pt/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pl creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pl/LC_MESSAGES copying build/lib/zapzap/po/pl/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/oc creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/oc/LC_MESSAGES copying build/lib/zapzap/po/oc/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/oc/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/nl creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/nl/LC_MESSAGES copying build/lib/zapzap/po/nl/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/nb_NO creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/nb_NO/LC_MESSAGES copying build/lib/zapzap/po/nb_NO/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/nb_NO/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/lv creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/lv/LC_MESSAGES copying build/lib/zapzap/po/lv/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/lt creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/lt/LC_MESSAGES copying build/lib/zapzap/po/lt/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ko creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ko/LC_MESSAGES copying build/lib/zapzap/po/ko/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/kn creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/kn/LC_MESSAGES copying build/lib/zapzap/po/kn/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/kmr creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/kmr/LC_MESSAGES copying build/lib/zapzap/po/kmr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/kmr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ka creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ka/LC_MESSAGES copying build/lib/zapzap/po/ka/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ja creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ja/LC_MESSAGES copying build/lib/zapzap/po/ja/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/it /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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.11/site-packages/setuptools/command/build_py.py:201: _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 /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/it/LC_MESSAGES copying build/lib/zapzap/po/it/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/it/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/id creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/id/LC_MESSAGES copying build/lib/zapzap/po/id/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/id/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hu creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hu/LC_MESSAGES copying build/lib/zapzap/po/hu/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hr creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hr/LC_MESSAGES copying build/lib/zapzap/po/hr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hi creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hi/LC_MESSAGES copying build/lib/zapzap/po/hi/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/he creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/he/LC_MESSAGES copying build/lib/zapzap/po/he/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/he/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/gl creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/gl/LC_MESSAGES copying build/lib/zapzap/po/gl/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fy creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fy/LC_MESSAGES copying build/lib/zapzap/po/fy/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fr creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fr/LC_MESSAGES copying build/lib/zapzap/po/fr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fi creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fi/LC_MESSAGES copying build/lib/zapzap/po/fi/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fa creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fa/LC_MESSAGES copying build/lib/zapzap/po/fa/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/eu creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/eu/LC_MESSAGES copying build/lib/zapzap/po/eu/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/es creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/es/LC_MESSAGES copying build/lib/zapzap/po/es/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/es/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/eo creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/eo/LC_MESSAGES copying build/lib/zapzap/po/eo/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/el creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/el/LC_MESSAGES copying build/lib/zapzap/po/el/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/el/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/de creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/de/LC_MESSAGES copying build/lib/zapzap/po/de/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/de/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/da creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/da/LC_MESSAGES copying build/lib/zapzap/po/da/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/da/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/cs creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/cs/LC_MESSAGES copying build/lib/zapzap/po/cs/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ca creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ca/LC_MESSAGES copying build/lib/zapzap/po/ca/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ar creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ar/LC_MESSAGES copying build/lib/zapzap/po/ar/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/am creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/am/LC_MESSAGES copying build/lib/zapzap/po/am/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/po/am/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/segoe-ui copying build/lib/zapzap/assets/segoe-ui/Segoe UI.ttf -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/segoe-ui copying build/lib/zapzap/assets/segoe-ui/Segoe UI Italic.ttf -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/segoe-ui copying build/lib/zapzap/assets/segoe-ui/Segoe UI Bold.ttf -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/segoe-ui copying build/lib/zapzap/assets/segoe-ui/Segoe UI Bold Italic.ttf -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/segoe-ui creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_settings.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_minimize_hover.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_minimize.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_maximize_hover.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_maximize.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_close_hover.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light copying build/lib/zapzap/assets/icons/titlebar_buttons/default/light/btn_close.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/light creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_settings.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_minimize_hover.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_minimize.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_maximize_hover.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_maximize.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_close_hover.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark copying build/lib/zapzap/assets/icons/titlebar_buttons/default/dark/btn_close.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/sponsor.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/pix.png -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/kofi.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/PayPal.png -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/banners creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/tray_light.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/tray_default.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/tray_dark.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/transparent.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/theme_system_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/theme_system_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/theme_light_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/theme_light_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/theme_dark_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/theme_dark_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/system.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/notifications.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/modelo.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/manage_accounts.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/home.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/expand_more.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/donations.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_unchecked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_indeterminate_disabled.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_indeterminate.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_checked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/borderDialog.png -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/border.png -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/appearance.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/about.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/light creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/tray_light.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/tray_default.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/tray_dark.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/transparent.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/theme_system_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/theme_system_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/theme_light_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/theme_light_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/theme_dark_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/theme_dark_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/system.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/notifications.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/manage_accounts.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/home.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/expand_more.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/donations.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_unchecked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_indeterminate_disabled.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_indeterminate.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_checked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_checked.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/borderDialog.png -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/border.png -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/appearance.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/about.svg -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/assets/icons/app/dark creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/model copying build/lib/zapzap/model/db.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/model copying build/lib/zapzap/model/user.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/model creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view copying build/lib/zapzap/view/card_user.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view copying build/lib/zapzap/view/downloadPopup.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view copying build/lib/zapzap/view/home.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view copying build/lib/zapzap/view/main_window.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view copying build/lib/zapzap/view/openChatPopup.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view copying build/lib/zapzap/view/settings.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme copying build/lib/zapzap/theme/builder_icon.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme copying build/lib/zapzap/theme/icons.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme copying build/lib/zapzap/theme/style.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme copying build/lib/zapzap/theme/zap_themes.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services copying build/lib/zapzap/services/dbus_notify.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services copying build/lib/zapzap/services/dbus_theme.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services copying build/lib/zapzap/services/portal_desktop.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services copying build/lib/zapzap/services/spellCheckLanguages.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/engine copying build/lib/zapzap/engine/browser.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/engine copying build/lib/zapzap/engine/whatsapp.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/engine creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration copying build/lib/zapzap/controllers/main_window_decoration/custom_grips.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration copying build/lib/zapzap/controllers/main_window_decoration/ui_actions.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration copying build/lib/zapzap/controllers/main_window_decoration/ui_decoration.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration creating /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/builder_icon.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/menu_bar.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/tray_icon.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/SingleApplication.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/card_user.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/download_popup.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/home.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/main_window.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/open_chat_popup.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/settings.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/user_container.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers copying build/lib/zapzap/__init__.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap copying build/lib/zapzap/__main__.py -> /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/model/db.py to db.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/model/user.py to user.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view/card_user.py to card_user.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view/downloadPopup.py to downloadPopup.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view/home.py to home.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view/main_window.py to main_window.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view/openChatPopup.py to openChatPopup.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/view/settings.py to settings.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme/builder_icon.py to builder_icon.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme/icons.py to icons.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme/style.py to style.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/theme/zap_themes.py to zap_themes.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services/dbus_notify.py to dbus_notify.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services/dbus_theme.py to dbus_theme.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services/portal_desktop.py to portal_desktop.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/services/spellCheckLanguages.py to spellCheckLanguages.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/engine/browser.py to browser.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/engine/whatsapp.py to whatsapp.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration/custom_grips.py to custom_grips.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration/ui_actions.py to ui_actions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_decoration/ui_decoration.py to ui_decoration.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components/builder_icon.py to builder_icon.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components/menu_bar.py to menu_bar.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window_components/tray_icon.py to tray_icon.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/SingleApplication.py to SingleApplication.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/card_user.py to card_user.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/download_popup.py to download_popup.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/home.py to home.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/main_window.py to main_window.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/open_chat_popup.py to open_chat_popup.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/settings.py to settings.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/controllers/user_container.py to user_container.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap/__main__.py to __main__.cpython-311.pyc running install_egg_info Copying zapzap.egg-info to /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11/site-packages/zapzap-4.4.6-py3.11.egg-info running install_scripts Installing zapzap script to /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/bin + mkdir -p /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/applications + mkdir -p /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/icons/hicolor/scalable/apps/ + cp -R share/applications/com.rtosta.zapzap.desktop /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/applications/com.rtosta.zapzap.desktop + cp -R share/icons/com.rtosta.zapzap.svg /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/icons/hicolor/scalable/apps/com.rtosta.zapzap.svg + /usr/bin/find-debuginfo -j2 --strict-build-id -m -i --build-id-seed 4.4.6-2.fc39 --unique-debug-suffix -4.4.6-2.fc39.x86_64 --unique-debug-src-base zapzap-4.4.6-2.fc39.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/zapzap-4.4.6 find: 'debug': No such file or directory + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j2 Bytecompiling .py files below /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/lib/python3.11 using python3.11 + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.gXnOwx + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd zapzap-4.4.6 + RPM_EC=0 ++ jobs -p + exit 0 Processing files: zapzap-4.4.6-2.fc39.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.ZGyZiQ + umask 022 + cd /builddir/build/BUILD + cd zapzap-4.4.6 + DOCDIR=/builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/doc/zapzap + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/doc/zapzap + cp -pr /builddir/build/BUILD/zapzap-4.4.6/README.md /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/doc/zapzap + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.tzIRZh + umask 022 + cd /builddir/build/BUILD + cd zapzap-4.4.6 + LICENSEDIR=/builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/licenses/zapzap + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/licenses/zapzap + cp -pr /builddir/build/BUILD/zapzap-4.4.6/LICENSE /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64/usr/share/licenses/zapzap + RPM_EC=0 ++ jobs -p + exit 0 Provides: application() application(com.rtosta.zapzap.desktop) mimehandler(x-scheme-handler/whatsapp) python3.11dist(zapzap) = 4.4.6 python3dist(zapzap) = 4.4.6 zapzap = 4.4.6-2.fc39 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: /usr/bin/python3 python(abi) = 3.11 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 Wrote: /builddir/build/RPMS/zapzap-4.4.6-2.fc39.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.6IO2X1 + umask 022 + cd /builddir/build/BUILD + cd zapzap-4.4.6 + /usr/bin/rm -rf /builddir/build/BUILDROOT/zapzap-4.4.6-2.fc39.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.14lrm1 + umask 022 + cd /builddir/build/BUILD + rm -rf zapzap-4.4.6 zapzap-4.4.6.gemspec + RPM_EC=0 ++ jobs -p + exit 0 Child return code was: 0