Warning: Permanently added '2620:52:3:1:dead:beef:cafe:c111' (ED25519) to the list of known hosts. You can reproduce this build on your computer by running: sudo dnf install copr-rpmbuild /usr/bin/copr-rpmbuild --verbose --drop-resultdir --task-url https://copr.fedorainfracloud.org/backend/get-build-task/8179436-fedora-39-x86_64 --chroot fedora-39-x86_64 Version: 1.1 PID: 6987 Logging PID: 6988 Task: {'allow_user_ssh': False, 'appstream': True, 'background': False, 'build_id': 8179436, 'buildroot_pkgs': [], 'chroot': 'fedora-39-x86_64', 'enable_net': True, 'fedora_review': True, 'git_hash': 'b9c58df685309badaaa8d687e3758873582ea1dc', 'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/rafatosta/zapzap/zapzap', 'isolation': 'default', 'memory_reqs': 2048, 'package_name': 'zapzap', 'package_version': '5.3.8-1', 'project_dirname': 'zapzap', 'project_name': 'zapzap', 'project_owner': 'rafatosta', 'repo_priority': None, 'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/rafatosta/zapzap/fedora-39-x86_64/', 'id': 'copr_base', 'name': 'Copr repository', 'priority': None}], 'sandbox': 'rafatosta/zapzap--rafatosta', 'source_json': {}, 'source_type': None, 'ssh_public_keys': None, 'storage': None, 'submitter': 'rafatosta', 'tags': [], 'task_id': '8179436-fedora-39-x86_64', 'timeout': 18000, 'uses_devel_repo': False, 'with_opts': [], 'without_opts': []} Running: git clone https://copr-dist-git.fedorainfracloud.org/git/rafatosta/zapzap/zapzap /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap --depth 500 --no-single-branch --recursive cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/rafatosta/zapzap/zapzap', '/var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap', '--depth', '500', '--no-single-branch', '--recursive'] cwd: . rc: 0 stdout: stderr: Cloning into '/var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap'... Running: git checkout b9c58df685309badaaa8d687e3758873582ea1dc -- cmd: ['git', 'checkout', 'b9c58df685309badaaa8d687e3758873582ea1dc', '--'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap rc: 0 stdout: stderr: Note: switching to 'b9c58df685309badaaa8d687e3758873582ea1dc'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false HEAD is now at b9c58df automatic import of zapzap Running: dist-git-client sources cmd: ['dist-git-client', 'sources'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap rc: 0 stdout: stderr: INFO: Reading stdout from command: git rev-parse --abbrev-ref HEAD INFO: Reading stdout from command: git rev-parse HEAD INFO: Reading sources specification file: sources INFO: Downloading 5.3.8.tar.gz INFO: Reading stdout from command: curl --help all INFO: Calling: curl -H Pragma: -o 5.3.8.tar.gz --location --connect-timeout 60 --retry 3 --retry-delay 10 --remote-time --show-error --fail --retry-all-errors https://copr-dist-git.fedorainfracloud.org/repo/pkgs/rafatosta/zapzap/zapzap/5.3.8.tar.gz/md5/f4d1728e44f31c2ea8d7419fa5763ca1/5.3.8.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1156k 100 1156k 0 0 13.1M 0 --:--:-- --:--:-- --:--:-- 13.2M INFO: Reading stdout from command: md5sum 5.3.8.tar.gz /usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated Running (timeout=18000): unbuffer mock --spec /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap/zapzap.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1729951987.459697 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 5.9 starting (python version = 3.12.1, NVR = mock-5.9-1.fc39), args: /usr/libexec/mock/mock --spec /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap/zapzap.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1729951987.459697 -r /var/lib/copr-rpmbuild/results/configs/child.cfg Start(bootstrap): init plugins INFO: tmpfs initialized INFO: selinux enabled INFO: chroot_scan: initialized INFO: compress_logs: initialized Finish(bootstrap): init plugins Start: init plugins INFO: tmpfs initialized INFO: selinux enabled INFO: chroot_scan: initialized INFO: compress_logs: initialized Finish: init plugins INFO: Signal handler active Start: run INFO: Start(/var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap/zapzap.spec) Config(fedora-39-x86_64) Start: clean chroot Finish: clean chroot Mock Version: 5.9 INFO: Mock Version: 5.9 Start(bootstrap): chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-39-x86_64-bootstrap-1729951987.459697/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata INFO: Guessed host environment type: unknown INFO: Using bootstrap image: registry.fedoraproject.org/fedora:39 INFO: Pulling image: registry.fedoraproject.org/fedora:39 INFO: Copy content of container registry.fedoraproject.org/fedora:39 to /var/lib/mock/fedora-39-x86_64-bootstrap-1729951987.459697/root INFO: Checking that registry.fedoraproject.org/fedora:39 image matches host's architecture INFO: mounting registry.fedoraproject.org/fedora:39 with podman image mount INFO: image registry.fedoraproject.org/fedora:39 as /var/lib/containers/storage/overlay/fbf2844bfb9d103a76fc639d0354deb6e42214e858f3ca8e58f970ec75362e0d/merged INFO: umounting image registry.fedoraproject.org/fedora:39 (/var/lib/containers/storage/overlay/fbf2844bfb9d103a76fc639d0354deb6e42214e858f3ca8e58f970ec75362e0d/merged) with podman image umount INFO: Package manager dnf4 detected and used (fallback) INFO: Bootstrap image not marked ready Start(bootstrap): installing dnf tooling No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 28 kB/s | 3.5 kB 00:00 fedora 16 MB/s | 89 MB 00:05 updates 8.7 MB/s | 42 MB 00:04 Package python3-dnf-4.21.1-1.fc39.noarch is already installed. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: python3-dnf-plugins-core noarch 4.9.0-1.fc39 updates 320 k Installing dependencies: dbus-libs x86_64 1:1.14.10-1.fc39 fedora 156 k python3-dateutil noarch 1:2.8.2-10.fc39 fedora 355 k python3-dbus x86_64 1.3.2-4.fc39 fedora 157 k python3-distro noarch 1.8.0-6.fc39 fedora 49 k python3-six noarch 1.16.0-12.fc39 fedora 41 k python3-systemd x86_64 235-5.fc39 fedora 107 k Transaction Summary ================================================================================ Install 7 Packages Total download size: 1.2 M Installed size: 3.6 M Downloading Packages: (1/7): dbus-libs-1.14.10-1.fc39.x86_64.rpm 1.1 MB/s | 156 kB 00:00 (2/7): python3-dbus-1.3.2-4.fc39.x86_64.rpm 1.1 MB/s | 157 kB 00:00 (3/7): python3-six-1.16.0-12.fc39.noarch.rpm 2.0 MB/s | 41 kB 00:00 (4/7): python3-distro-1.8.0-6.fc39.noarch.rpm 2.2 MB/s | 49 kB 00:00 (5/7): python3-dateutil-2.8.2-10.fc39.noarch.rp 2.1 MB/s | 355 kB 00:00 (6/7): python3-systemd-235-5.fc39.x86_64.rpm 4.0 MB/s | 107 kB 00:00 (7/7): python3-dnf-plugins-core-4.9.0-1.fc39.no 2.9 MB/s | 320 kB 00:00 -------------------------------------------------------------------------------- Total 3.5 MB/s | 1.2 MB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python3-systemd-235-5.fc39.x86_64 1/7 Installing : python3-six-1.16.0-12.fc39.noarch 2/7 Installing : python3-dateutil-1:2.8.2-10.fc39.noarch 3/7 Installing : python3-distro-1.8.0-6.fc39.noarch 4/7 Installing : dbus-libs-1:1.14.10-1.fc39.x86_64 5/7 Installing : python3-dbus-1.3.2-4.fc39.x86_64 6/7 Installing : python3-dnf-plugins-core-4.9.0-1.fc39.noarch 7/7 Running scriptlet: python3-dnf-plugins-core-4.9.0-1.fc39.noarch 7/7 Verifying : dbus-libs-1:1.14.10-1.fc39.x86_64 1/7 Verifying : python3-dateutil-1:2.8.2-10.fc39.noarch 2/7 Verifying : python3-dbus-1.3.2-4.fc39.x86_64 3/7 Verifying : python3-distro-1.8.0-6.fc39.noarch 4/7 Verifying : python3-six-1.16.0-12.fc39.noarch 5/7 Verifying : python3-systemd-235-5.fc39.x86_64 6/7 Verifying : python3-dnf-plugins-core-4.9.0-1.fc39.noarch 7/7 Installed: dbus-libs-1:1.14.10-1.fc39.x86_64 python3-dateutil-1:2.8.2-10.fc39.noarch python3-dbus-1.3.2-4.fc39.x86_64 python3-distro-1.8.0-6.fc39.noarch python3-dnf-plugins-core-4.9.0-1.fc39.noarch python3-six-1.16.0-12.fc39.noarch python3-systemd-235-5.fc39.x86_64 Complete! Finish(bootstrap): installing dnf tooling Start(bootstrap): creating root cache Finish(bootstrap): creating root cache Finish(bootstrap): chroot init Start: chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-39-x86_64-1729951987.459697/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin INFO: Package manager dnf4 detected and used (direct choice) INFO: Buildroot is handled by package management downloaded with a bootstrap image: rpm-4.19.1.1-1.fc39.x86_64 rpm-sequoia-1.7.0-1.fc39.x86_64 python3-dnf-4.21.1-1.fc39.noarch python3-dnf-plugins-core-4.9.0-1.fc39.noarch yum-4.21.1-1.fc39.noarch Start: installing minimal buildroot with dnf No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 44 kB/s | 3.5 kB 00:00 fedora 32 MB/s | 89 MB 00:02 updates 2.6 MB/s | 42 MB 00:15 Dependencies resolved. ================================================================================ Package Arch Version Repo Size ================================================================================ Installing group/module packages: bash x86_64 5.2.26-1.fc39 updates 1.8 M bzip2 x86_64 1.0.8-16.fc39 fedora 52 k coreutils x86_64 9.3-7.fc39 updates 1.1 M cpio x86_64 2.14-4.fc39 fedora 279 k diffutils x86_64 3.10-3.fc39 fedora 398 k fedora-release-common noarch 39-36 updates 19 k findutils x86_64 1:4.9.0-6.fc39 updates 490 k gawk x86_64 5.2.2-2.fc39 fedora 1.1 M glibc-minimal-langpack x86_64 2.38-18.fc39 updates 73 k grep x86_64 3.11-3.fc39 fedora 298 k gzip x86_64 1.12-6.fc39 fedora 166 k info x86_64 7.0.3-3.fc39 fedora 182 k patch x86_64 2.7.6-22.fc39 fedora 125 k redhat-rpm-config noarch 266-1.fc39 updates 78 k rpm-build x86_64 4.19.1.1-1.fc39 updates 78 k sed x86_64 4.8-14.fc39 fedora 306 k shadow-utils x86_64 2:4.14.0-2.fc39 updates 1.3 M tar x86_64 2:1.35-2.fc39 fedora 864 k unzip x86_64 6.0-62.fc39 fedora 184 k util-linux x86_64 2.39.4-1.fc39 updates 1.2 M which x86_64 2.21-40.fc39 fedora 42 k xz x86_64 5.4.4-1.fc39 fedora 556 k Installing dependencies: alternatives x86_64 1.26-1.fc39 updates 39 k ansible-srpm-macros noarch 1-12.fc39 updates 21 k audit-libs x86_64 3.1.5-1.fc39 updates 123 k authselect x86_64 1.4.3-1.fc39 fedora 149 k authselect-libs x86_64 1.4.3-1.fc39 fedora 249 k basesystem noarch 11-18.fc39 fedora 7.2 k binutils x86_64 2.40-14.fc39 updates 5.6 M binutils-gold x86_64 2.40-14.fc39 updates 795 k bzip2-libs x86_64 1.0.8-16.fc39 fedora 41 k ca-certificates noarch 2024.2.69_v8.0.401-1.0.fc39 updates 871 k coreutils-common x86_64 9.3-7.fc39 updates 2.1 M cracklib x86_64 2.9.11-2.fc39 fedora 94 k crypto-policies noarch 20231204-1.git1e3a2e4.fc39 updates 100 k curl x86_64 8.2.1-5.fc39 updates 344 k cyrus-sasl-lib x86_64 2.1.28-11.fc39 fedora 793 k debugedit x86_64 5.0-12.fc39 updates 79 k dwz x86_64 0.15-3.fc39 fedora 134 k ed x86_64 1.19-4.fc39 fedora 79 k efi-srpm-macros noarch 5-9.fc39 fedora 22 k elfutils x86_64 0.191-2.fc39 updates 559 k elfutils-debuginfod-client x86_64 0.191-2.fc39 updates 38 k elfutils-default-yama-scope noarch 0.191-2.fc39 updates 13 k elfutils-libelf x86_64 0.191-2.fc39 updates 209 k elfutils-libs x86_64 0.191-2.fc39 updates 263 k fedora-gpg-keys noarch 39-2 updates 130 k fedora-release noarch 39-36 updates 8.6 k fedora-release-identity-basic noarch 39-36 updates 9.4 k fedora-repos noarch 39-2 updates 9.3 k file x86_64 5.44-5.fc39 fedora 49 k file-libs x86_64 5.44-5.fc39 fedora 729 k filesystem x86_64 3.18-6.fc39 fedora 1.1 M fonts-srpm-macros noarch 1:2.0.5-12.fc39 fedora 26 k forge-srpm-macros noarch 0.3.1-1.fc39 updates 19 k fpc-srpm-macros noarch 1.3-8.fc39 fedora 7.4 k gdb-minimal x86_64 15.1-1.fc39 updates 4.3 M gdbm-libs x86_64 1:1.23-4.fc39 fedora 56 k ghc-srpm-macros noarch 1.6.1-2.fc39 fedora 7.8 k glibc x86_64 2.38-18.fc39 updates 2.2 M glibc-common x86_64 2.38-18.fc39 updates 353 k glibc-gconv-extra x86_64 2.38-18.fc39 updates 1.6 M gmp x86_64 1:6.2.1-5.fc39 fedora 313 k gnat-srpm-macros noarch 6-3.fc39 fedora 8.8 k go-srpm-macros noarch 3.5.0-1.fc39 updates 28 k jansson x86_64 2.13.1-7.fc39 fedora 44 k kernel-srpm-macros noarch 1.0-20.fc39 fedora 10 k keyutils-libs x86_64 1.6.3-1.fc39 updates 31 k krb5-libs x86_64 1.21.3-1.fc39 updates 764 k libacl x86_64 2.3.1-9.fc39 updates 23 k libarchive x86_64 3.7.1-2.fc39 updates 407 k libattr x86_64 2.5.1-8.fc39 fedora 18 k libblkid x86_64 2.39.4-1.fc39 updates 116 k libbrotli x86_64 1.1.0-1.fc39 fedora 336 k libcap x86_64 2.48-9.fc39 updates 68 k libcap-ng x86_64 0.8.3-8.fc39 fedora 32 k libcom_err x86_64 1.47.0-2.fc39 fedora 26 k libcurl x86_64 8.2.1-5.fc39 updates 322 k libdb x86_64 5.3.28-56.fc39 fedora 760 k libeconf x86_64 0.5.2-2.fc39 updates 30 k libevent x86_64 2.1.12-9.fc39 fedora 258 k libfdisk x86_64 2.39.4-1.fc39 updates 161 k libffi x86_64 3.4.4-4.fc39 fedora 40 k libgcc x86_64 13.3.1-3.fc39 updates 120 k libgomp x86_64 13.3.1-3.fc39 updates 329 k libidn2 x86_64 2.3.7-1.fc39 updates 119 k libmount x86_64 2.39.4-1.fc39 updates 154 k libnghttp2 x86_64 1.55.1-5.fc39 updates 75 k libnsl2 x86_64 2.0.0-6.fc39 fedora 30 k libpkgconf x86_64 1.9.5-2.fc39 fedora 38 k libpsl x86_64 0.21.2-4.fc39 fedora 63 k libpwquality x86_64 1.4.5-6.fc39 fedora 120 k libselinux x86_64 3.5-5.fc39 fedora 87 k libsemanage x86_64 3.5-4.fc39 fedora 120 k libsepol x86_64 3.5-2.fc39 fedora 324 k libsigsegv x86_64 2.14-5.fc39 fedora 27 k libsmartcols x86_64 2.39.4-1.fc39 updates 67 k libssh x86_64 0.10.6-2.fc39 updates 212 k libssh-config noarch 0.10.6-2.fc39 updates 9.0 k libstdc++ x86_64 13.3.1-3.fc39 updates 870 k libtasn1 x86_64 4.19.0-3.fc39 fedora 74 k libtirpc x86_64 1.3.5-0.fc39 updates 94 k libtool-ltdl x86_64 2.4.7-7.fc39 fedora 36 k libunistring x86_64 1.1-5.fc39 fedora 543 k libutempter x86_64 1.2.1-10.fc39 fedora 26 k libuuid x86_64 2.39.4-1.fc39 updates 28 k libverto x86_64 0.3.2-6.fc39 fedora 20 k libxcrypt x86_64 4.4.36-2.fc39 fedora 119 k libxml2 x86_64 2.10.4-3.fc39 fedora 701 k libzstd x86_64 1.5.6-1.fc39 updates 312 k lua-libs x86_64 5.4.6-3.fc39 fedora 133 k lua-srpm-macros noarch 1-13.fc39 updates 8.7 k lz4-libs x86_64 1.9.4-4.fc39 fedora 67 k mpfr x86_64 4.2.0-3.fc39 fedora 344 k ncurses-base noarch 6.4-7.20230520.fc39.1 updates 88 k ncurses-libs x86_64 6.4-7.20230520.fc39.1 updates 336 k ocaml-srpm-macros noarch 8-2.fc39 fedora 14 k openblas-srpm-macros noarch 2-14.fc39 fedora 7.5 k openldap x86_64 2.6.7-1.fc39 updates 254 k openssl-libs x86_64 1:3.1.4-4.fc39 updates 2.2 M p11-kit x86_64 0.25.5-1.fc39 updates 515 k p11-kit-trust x86_64 0.25.5-1.fc39 updates 138 k package-notes-srpm-macros noarch 0.5-9.fc39 fedora 11 k pam x86_64 1.5.3-3.fc39 updates 542 k pam-libs x86_64 1.5.3-3.fc39 updates 56 k pcre2 x86_64 10.42-1.fc39.2 fedora 233 k pcre2-syntax noarch 10.42-1.fc39.2 fedora 143 k perl-srpm-macros noarch 1-51.fc39 fedora 8.0 k pkgconf x86_64 1.9.5-2.fc39 fedora 42 k pkgconf-m4 noarch 1.9.5-2.fc39 fedora 14 k pkgconf-pkg-config x86_64 1.9.5-2.fc39 fedora 9.6 k popt x86_64 1.19-3.fc39 fedora 66 k publicsuffix-list-dafsa noarch 20240107-1.fc39 updates 58 k pyproject-srpm-macros noarch 1.15.1-1.fc39 updates 13 k python-srpm-macros noarch 3.12-8.fc39 updates 23 k qt5-srpm-macros noarch 5.15.14-2.fc39 updates 8.9 k qt6-srpm-macros noarch 6.6.2-1.fc39 updates 8.9 k readline x86_64 8.2-6.fc39 updates 212 k rpm x86_64 4.19.1.1-1.fc39 updates 538 k rpm-build-libs x86_64 4.19.1.1-1.fc39 updates 95 k rpm-libs x86_64 4.19.1.1-1.fc39 updates 312 k rpm-sequoia x86_64 1.7.0-1.fc39 updates 904 k rpmautospec-rpm-macros noarch 0.7.2-1.fc39 updates 10 k rust-srpm-macros noarch 26.3-1.fc39 updates 13 k setup noarch 2.14.4-1.fc39 fedora 154 k sqlite-libs x86_64 3.42.0-7.fc39 fedora 678 k systemd-libs x86_64 254.18-1.fc39 updates 682 k util-linux-core x86_64 2.39.4-1.fc39 updates 507 k xxhash-libs x86_64 0.8.2-4.fc39 updates 37 k xz-libs x86_64 5.4.4-1.fc39 fedora 108 k zip x86_64 3.0-39.fc39 fedora 266 k zlib x86_64 1.2.13-4.fc39 fedora 94 k zstd x86_64 1.5.6-1.fc39 updates 479 k Installing Groups: Buildsystem building group Transaction Summary ================================================================================ Install 153 Packages Total download size: 52 M Installed size: 179 M Downloading Packages: (1/153): basesystem-11-18.fc39.noarch.rpm 121 kB/s | 7.2 kB 00:00 (2/153): bzip2-1.0.8-16.fc39.x86_64.rpm 695 kB/s | 52 kB 00:00 (3/153): authselect-1.4.3-1.fc39.x86_64.rpm 937 kB/s | 149 kB 00:00 (4/153): bzip2-libs-1.0.8-16.fc39.x86_64.rpm 1.2 MB/s | 41 kB 00:00 (5/153): authselect-libs-1.4.3-1.fc39.x86_64.rp 1.4 MB/s | 249 kB 00:00 (6/153): cpio-2.14-4.fc39.x86_64.rpm 4.8 MB/s | 279 kB 00:00 (7/153): cracklib-2.9.11-2.fc39.x86_64.rpm 1.8 MB/s | 94 kB 00:00 (8/153): cyrus-sasl-lib-2.1.28-11.fc39.x86_64.r 9.9 MB/s | 793 kB 00:00 (9/153): diffutils-3.10-3.fc39.x86_64.rpm 11 MB/s | 398 kB 00:00 (10/153): dwz-0.15-3.fc39.x86_64.rpm 3.8 MB/s | 134 kB 00:00 (11/153): ed-1.19-4.fc39.x86_64.rpm 2.8 MB/s | 79 kB 00:00 (12/153): efi-srpm-macros-5-9.fc39.noarch.rpm 881 kB/s | 22 kB 00:00 (13/153): file-5.44-5.fc39.x86_64.rpm 1.8 MB/s | 49 kB 00:00 (14/153): fonts-srpm-macros-2.0.5-12.fc39.noarc 945 kB/s | 26 kB 00:00 (15/153): file-libs-5.44-5.fc39.x86_64.rpm 19 MB/s | 729 kB 00:00 (16/153): fpc-srpm-macros-1.3-8.fc39.noarch.rpm 291 kB/s | 7.4 kB 00:00 (17/153): filesystem-3.18-6.fc39.x86_64.rpm 18 MB/s | 1.1 MB 00:00 (18/153): gdbm-libs-1.23-4.fc39.x86_64.rpm 2.0 MB/s | 56 kB 00:00 (19/153): ghc-srpm-macros-1.6.1-2.fc39.noarch.r 307 kB/s | 7.8 kB 00:00 (20/153): gawk-5.2.2-2.fc39.x86_64.rpm 20 MB/s | 1.1 MB 00:00 (21/153): gnat-srpm-macros-6-3.fc39.noarch.rpm 347 kB/s | 8.8 kB 00:00 (22/153): gmp-6.2.1-5.fc39.x86_64.rpm 11 MB/s | 313 kB 00:00 (23/153): grep-3.11-3.fc39.x86_64.rpm 10 MB/s | 298 kB 00:00 (24/153): info-7.0.3-3.fc39.x86_64.rpm 5.9 MB/s | 182 kB 00:00 (25/153): gzip-1.12-6.fc39.x86_64.rpm 4.7 MB/s | 166 kB 00:00 (26/153): jansson-2.13.1-7.fc39.x86_64.rpm 1.7 MB/s | 44 kB 00:00 (27/153): kernel-srpm-macros-1.0-20.fc39.noarch 416 kB/s | 10 kB 00:00 (28/153): libattr-2.5.1-8.fc39.x86_64.rpm 698 kB/s | 18 kB 00:00 (29/153): libcap-ng-0.8.3-8.fc39.x86_64.rpm 1.2 MB/s | 32 kB 00:00 (30/153): libcom_err-1.47.0-2.fc39.x86_64.rpm 1.0 MB/s | 26 kB 00:00 (31/153): libbrotli-1.1.0-1.fc39.x86_64.rpm 6.3 MB/s | 336 kB 00:00 (32/153): libffi-3.4.4-4.fc39.x86_64.rpm 1.4 MB/s | 40 kB 00:00 (33/153): libevent-2.1.12-9.fc39.x86_64.rpm 8.3 MB/s | 258 kB 00:00 (34/153): libdb-5.3.28-56.fc39.x86_64.rpm 21 MB/s | 760 kB 00:00 (35/153): libnsl2-2.0.0-6.fc39.x86_64.rpm 1.1 MB/s | 30 kB 00:00 (36/153): libpkgconf-1.9.5-2.fc39.x86_64.rpm 1.4 MB/s | 38 kB 00:00 (37/153): libpsl-0.21.2-4.fc39.x86_64.rpm 2.3 MB/s | 63 kB 00:00 (38/153): libpwquality-1.4.5-6.fc39.x86_64.rpm 4.2 MB/s | 120 kB 00:00 (39/153): libselinux-3.5-5.fc39.x86_64.rpm 3.2 MB/s | 87 kB 00:00 (40/153): libsemanage-3.5-4.fc39.x86_64.rpm 4.3 MB/s | 120 kB 00:00 (41/153): libsigsegv-2.14-5.fc39.x86_64.rpm 1.0 MB/s | 27 kB 00:00 (42/153): libsepol-3.5-2.fc39.x86_64.rpm 10 MB/s | 324 kB 00:00 (43/153): libtasn1-4.19.0-3.fc39.x86_64.rpm 2.7 MB/s | 74 kB 00:00 (44/153): libtool-ltdl-2.4.7-7.fc39.x86_64.rpm 1.4 MB/s | 36 kB 00:00 (45/153): libutempter-1.2.1-10.fc39.x86_64.rpm 1.0 MB/s | 26 kB 00:00 (46/153): libverto-0.3.2-6.fc39.x86_64.rpm 809 kB/s | 20 kB 00:00 (47/153): libunistring-1.1-5.fc39.x86_64.rpm 9.9 MB/s | 543 kB 00:00 (48/153): libxcrypt-4.4.36-2.fc39.x86_64.rpm 4.3 MB/s | 119 kB 00:00 (49/153): libxml2-2.10.4-3.fc39.x86_64.rpm 20 MB/s | 701 kB 00:00 (50/153): lz4-libs-1.9.4-4.fc39.x86_64.rpm 2.4 MB/s | 67 kB 00:00 (51/153): lua-libs-5.4.6-3.fc39.x86_64.rpm 4.6 MB/s | 133 kB 00:00 (52/153): ocaml-srpm-macros-8-2.fc39.noarch.rpm 528 kB/s | 14 kB 00:00 (53/153): openblas-srpm-macros-2-14.fc39.noarch 297 kB/s | 7.5 kB 00:00 (54/153): mpfr-4.2.0-3.fc39.x86_64.rpm 11 MB/s | 344 kB 00:00 (55/153): package-notes-srpm-macros-0.5-9.fc39. 440 kB/s | 11 kB 00:00 (56/153): patch-2.7.6-22.fc39.x86_64.rpm 4.4 MB/s | 125 kB 00:00 (57/153): pcre2-10.42-1.fc39.2.x86_64.rpm 7.9 MB/s | 233 kB 00:00 (58/153): pcre2-syntax-10.42-1.fc39.2.noarch.rp 5.0 MB/s | 143 kB 00:00 (59/153): perl-srpm-macros-1-51.fc39.noarch.rpm 309 kB/s | 8.0 kB 00:00 (60/153): pkgconf-1.9.5-2.fc39.x86_64.rpm 1.6 MB/s | 42 kB 00:00 (61/153): pkgconf-pkg-config-1.9.5-2.fc39.x86_6 377 kB/s | 9.6 kB 00:00 (62/153): pkgconf-m4-1.9.5-2.fc39.noarch.rpm 530 kB/s | 14 kB 00:00 (63/153): popt-1.19-3.fc39.x86_64.rpm 2.4 MB/s | 66 kB 00:00 (64/153): setup-2.14.4-1.fc39.noarch.rpm 5.2 MB/s | 154 kB 00:00 (65/153): sed-4.8-14.fc39.x86_64.rpm 9.8 MB/s | 306 kB 00:00 (66/153): sqlite-libs-3.42.0-7.fc39.x86_64.rpm 20 MB/s | 678 kB 00:00 (67/153): unzip-6.0-62.fc39.x86_64.rpm 6.5 MB/s | 184 kB 00:00 (68/153): which-2.21-40.fc39.x86_64.rpm 1.6 MB/s | 42 kB 00:00 (69/153): tar-1.35-2.fc39.x86_64.rpm 22 MB/s | 864 kB 00:00 (70/153): xz-5.4.4-1.fc39.x86_64.rpm 18 MB/s | 556 kB 00:00 (71/153): xz-libs-5.4.4-1.fc39.x86_64.rpm 3.9 MB/s | 108 kB 00:00 (72/153): zip-3.0-39.fc39.x86_64.rpm 9.4 MB/s | 266 kB 00:00 (73/153): zlib-1.2.13-4.fc39.x86_64.rpm 3.4 MB/s | 94 kB 00:00 (74/153): ansible-srpm-macros-1-12.fc39.noarch. 94 kB/s | 21 kB 00:00 (75/153): alternatives-1.26-1.fc39.x86_64.rpm 166 kB/s | 39 kB 00:00 (76/153): audit-libs-3.1.5-1.fc39.x86_64.rpm 406 kB/s | 123 kB 00:00 (77/153): binutils-gold-2.40-14.fc39.x86_64.rpm 4.0 MB/s | 795 kB 00:00 (78/153): bash-5.2.26-1.fc39.x86_64.rpm 5.4 MB/s | 1.8 MB 00:00 (79/153): ca-certificates-2024.2.69_v8.0.401-1. 10 MB/s | 871 kB 00:00 (80/153): coreutils-9.3-7.fc39.x86_64.rpm 15 MB/s | 1.1 MB 00:00 (81/153): binutils-2.40-14.fc39.x86_64.rpm 14 MB/s | 5.6 MB 00:00 (82/153): crypto-policies-20231204-1.git1e3a2e4 2.0 MB/s | 100 kB 00:00 (83/153): curl-8.2.1-5.fc39.x86_64.rpm 6.2 MB/s | 344 kB 00:00 (84/153): coreutils-common-9.3-7.fc39.x86_64.rp 18 MB/s | 2.1 MB 00:00 (85/153): debugedit-5.0-12.fc39.x86_64.rpm 1.6 MB/s | 79 kB 00:00 (86/153): elfutils-0.191-2.fc39.x86_64.rpm 9.3 MB/s | 559 kB 00:00 (87/153): elfutils-debuginfod-client-0.191-2.fc 794 kB/s | 38 kB 00:00 (88/153): elfutils-default-yama-scope-0.191-2.f 276 kB/s | 13 kB 00:00 (89/153): elfutils-libelf-0.191-2.fc39.x86_64.r 4.0 MB/s | 209 kB 00:00 (90/153): elfutils-libs-0.191-2.fc39.x86_64.rpm 5.0 MB/s | 263 kB 00:00 (91/153): fedora-gpg-keys-39-2.noarch.rpm 2.6 MB/s | 130 kB 00:00 (92/153): fedora-release-39-36.noarch.rpm 179 kB/s | 8.6 kB 00:00 (93/153): fedora-release-common-39-36.noarch.rp 394 kB/s | 19 kB 00:00 (94/153): fedora-release-identity-basic-39-36.n 193 kB/s | 9.4 kB 00:00 (95/153): fedora-repos-39-2.noarch.rpm 192 kB/s | 9.3 kB 00:00 (96/153): findutils-4.9.0-6.fc39.x86_64.rpm 8.8 MB/s | 490 kB 00:00 (97/153): forge-srpm-macros-0.3.1-1.fc39.noarch 405 kB/s | 19 kB 00:00 (98/153): glibc-common-2.38-18.fc39.x86_64.rpm 6.1 MB/s | 353 kB 00:00 (99/153): glibc-gconv-extra-2.38-18.fc39.x86_64 25 MB/s | 1.6 MB 00:00 (100/153): glibc-2.38-18.fc39.x86_64.rpm 16 MB/s | 2.2 MB 00:00 (101/153): gdb-minimal-15.1-1.fc39.x86_64.rpm 26 MB/s | 4.3 MB 00:00 (102/153): glibc-minimal-langpack-2.38-18.fc39. 1.4 MB/s | 73 kB 00:00 (103/153): go-srpm-macros-3.5.0-1.fc39.noarch.r 577 kB/s | 28 kB 00:00 (104/153): keyutils-libs-1.6.3-1.fc39.x86_64.rp 650 kB/s | 31 kB 00:00 (105/153): krb5-libs-1.21.3-1.fc39.x86_64.rpm 13 MB/s | 764 kB 00:00 (106/153): libacl-2.3.1-9.fc39.x86_64.rpm 487 kB/s | 23 kB 00:00 (107/153): libarchive-3.7.1-2.fc39.x86_64.rpm 7.6 MB/s | 407 kB 00:00 (108/153): libblkid-2.39.4-1.fc39.x86_64.rpm 2.3 MB/s | 116 kB 00:00 (109/153): libcap-2.48-9.fc39.x86_64.rpm 1.3 MB/s | 68 kB 00:00 (110/153): libcurl-8.2.1-5.fc39.x86_64.rpm 6.0 MB/s | 322 kB 00:00 (111/153): libeconf-0.5.2-2.fc39.x86_64.rpm 616 kB/s | 30 kB 00:00 (112/153): libfdisk-2.39.4-1.fc39.x86_64.rpm 3.1 MB/s | 161 kB 00:00 (113/153): libgcc-13.3.1-3.fc39.x86_64.rpm 2.4 MB/s | 120 kB 00:00 (114/153): libidn2-2.3.7-1.fc39.x86_64.rpm 2.3 MB/s | 119 kB 00:00 (115/153): libgomp-13.3.1-3.fc39.x86_64.rpm 6.1 MB/s | 329 kB 00:00 (116/153): libmount-2.39.4-1.fc39.x86_64.rpm 3.0 MB/s | 154 kB 00:00 (117/153): libnghttp2-1.55.1-5.fc39.x86_64.rpm 1.5 MB/s | 75 kB 00:00 (118/153): libsmartcols-2.39.4-1.fc39.x86_64.rp 1.3 MB/s | 67 kB 00:00 (119/153): libssh-0.10.6-2.fc39.x86_64.rpm 4.1 MB/s | 212 kB 00:00 (120/153): libssh-config-0.10.6-2.fc39.noarch.r 187 kB/s | 9.0 kB 00:00 (121/153): libstdc++-13.3.1-3.fc39.x86_64.rpm 15 MB/s | 870 kB 00:00 (122/153): libtirpc-1.3.5-0.fc39.x86_64.rpm 1.8 MB/s | 94 kB 00:00 (123/153): libuuid-2.39.4-1.fc39.x86_64.rpm 569 kB/s | 28 kB 00:00 (124/153): libzstd-1.5.6-1.fc39.x86_64.rpm 5.8 MB/s | 312 kB 00:00 (125/153): lua-srpm-macros-1-13.fc39.noarch.rpm 178 kB/s | 8.7 kB 00:00 (126/153): ncurses-base-6.4-7.20230520.fc39.1.n 1.7 MB/s | 88 kB 00:00 (127/153): ncurses-libs-6.4-7.20230520.fc39.1.x 6.2 MB/s | 336 kB 00:00 (128/153): openldap-2.6.7-1.fc39.x86_64.rpm 4.6 MB/s | 254 kB 00:00 (129/153): p11-kit-trust-0.25.5-1.fc39.x86_64.r 2.5 MB/s | 138 kB 00:00 (130/153): p11-kit-0.25.5-1.fc39.x86_64.rpm 8.6 MB/s | 515 kB 00:00 (131/153): openssl-libs-3.1.4-4.fc39.x86_64.rpm 27 MB/s | 2.2 MB 00:00 (132/153): pam-libs-1.5.3-3.fc39.x86_64.rpm 1.1 MB/s | 56 kB 00:00 (133/153): pam-1.5.3-3.fc39.x86_64.rpm 9.6 MB/s | 542 kB 00:00 (134/153): publicsuffix-list-dafsa-20240107-1.f 1.2 MB/s | 58 kB 00:00 (135/153): pyproject-srpm-macros-1.15.1-1.fc39. 278 kB/s | 13 kB 00:00 (136/153): python-srpm-macros-3.12-8.fc39.noarc 487 kB/s | 23 kB 00:00 (137/153): qt5-srpm-macros-5.15.14-2.fc39.noarc 187 kB/s | 8.9 kB 00:00 (138/153): qt6-srpm-macros-6.6.2-1.fc39.noarch. 185 kB/s | 8.9 kB 00:00 (139/153): readline-8.2-6.fc39.x86_64.rpm 4.1 MB/s | 212 kB 00:00 (140/153): redhat-rpm-config-266-1.fc39.noarch. 1.5 MB/s | 78 kB 00:00 (141/153): rpm-4.19.1.1-1.fc39.x86_64.rpm 9.6 MB/s | 538 kB 00:00 (142/153): rpm-build-4.19.1.1-1.fc39.x86_64.rpm 1.5 MB/s | 78 kB 00:00 (143/153): rpm-build-libs-4.19.1.1-1.fc39.x86_6 1.8 MB/s | 95 kB 00:00 (144/153): rpmautospec-rpm-macros-0.7.2-1.fc39. 216 kB/s | 10 kB 00:00 (145/153): rpm-libs-4.19.1.1-1.fc39.x86_64.rpm 5.9 MB/s | 312 kB 00:00 (146/153): rpm-sequoia-1.7.0-1.fc39.x86_64.rpm 15 MB/s | 904 kB 00:00 (147/153): rust-srpm-macros-26.3-1.fc39.noarch. 262 kB/s | 13 kB 00:00 (148/153): shadow-utils-4.14.0-2.fc39.x86_64.rp 20 MB/s | 1.3 MB 00:00 (149/153): systemd-libs-254.18-1.fc39.x86_64.rp 11 MB/s | 682 kB 00:00 (150/153): util-linux-2.39.4-1.fc39.x86_64.rpm 18 MB/s | 1.2 MB 00:00 (151/153): util-linux-core-2.39.4-1.fc39.x86_64 9.1 MB/s | 507 kB 00:00 (152/153): xxhash-libs-0.8.2-4.fc39.x86_64.rpm 728 kB/s | 37 kB 00:00 (153/153): zstd-1.5.6-1.fc39.x86_64.rpm 8.6 MB/s | 479 kB 00:00 -------------------------------------------------------------------------------- Total 18 MB/s | 52 MB 00:02 fedora 1.6 MB/s | 1.6 kB 00:00 Importing GPG key 0x18B8E74C: Userid : "Fedora (39) " Fingerprint: E8F2 3996 F232 1864 0CB4 4CBE 75CF 5AC4 18B8 E74C From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-39-primary Key imported successfully Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: filesystem-3.18-6.fc39.x86_64 1/1 Preparing : 1/1 Installing : libgcc-13.3.1-3.fc39.x86_64 1/153 Running scriptlet: libgcc-13.3.1-3.fc39.x86_64 1/153 Installing : crypto-policies-20231204-1.git1e3a2e4.fc39.noarc 2/153 Running scriptlet: crypto-policies-20231204-1.git1e3a2e4.fc39.noarc 2/153 Installing : fedora-release-identity-basic-39-36.noarch 3/153 Installing : fedora-gpg-keys-39-2.noarch 4/153 Installing : fedora-repos-39-2.noarch 5/153 Installing : fedora-release-common-39-36.noarch 6/153 Installing : fedora-release-39-36.noarch 7/153 Installing : setup-2.14.4-1.fc39.noarch 8/153 Running scriptlet: setup-2.14.4-1.fc39.noarch 8/153 Installing : filesystem-3.18-6.fc39.x86_64 9/153 Installing : basesystem-11-18.fc39.noarch 10/153 Installing : rust-srpm-macros-26.3-1.fc39.noarch 11/153 Installing : qt6-srpm-macros-6.6.2-1.fc39.noarch 12/153 Installing : qt5-srpm-macros-5.15.14-2.fc39.noarch 13/153 Installing : publicsuffix-list-dafsa-20240107-1.fc39.noarch 14/153 Installing : ncurses-base-6.4-7.20230520.fc39.1.noarch 15/153 Installing : glibc-gconv-extra-2.38-18.fc39.x86_64 16/153 Running scriptlet: glibc-gconv-extra-2.38-18.fc39.x86_64 16/153 Installing : glibc-minimal-langpack-2.38-18.fc39.x86_64 17/153 Installing : glibc-common-2.38-18.fc39.x86_64 18/153 Running scriptlet: glibc-2.38-18.fc39.x86_64 19/153 Installing : glibc-2.38-18.fc39.x86_64 19/153 Running scriptlet: glibc-2.38-18.fc39.x86_64 19/153 Installing : ncurses-libs-6.4-7.20230520.fc39.1.x86_64 20/153 Installing : bash-5.2.26-1.fc39.x86_64 21/153 Running scriptlet: bash-5.2.26-1.fc39.x86_64 21/153 Installing : zlib-1.2.13-4.fc39.x86_64 22/153 Installing : xz-libs-5.4.4-1.fc39.x86_64 23/153 Installing : bzip2-libs-1.0.8-16.fc39.x86_64 24/153 Installing : popt-1.19-3.fc39.x86_64 25/153 Installing : libstdc++-13.3.1-3.fc39.x86_64 26/153 Installing : libuuid-2.39.4-1.fc39.x86_64 27/153 Installing : libzstd-1.5.6-1.fc39.x86_64 28/153 Installing : elfutils-libelf-0.191-2.fc39.x86_64 29/153 Installing : libblkid-2.39.4-1.fc39.x86_64 30/153 Installing : readline-8.2-6.fc39.x86_64 31/153 Installing : gmp-1:6.2.1-5.fc39.x86_64 32/153 Installing : libattr-2.5.1-8.fc39.x86_64 33/153 Installing : libacl-2.3.1-9.fc39.x86_64 34/153 Installing : libxcrypt-4.4.36-2.fc39.x86_64 35/153 Installing : libcap-2.48-9.fc39.x86_64 36/153 Installing : lz4-libs-1.9.4-4.fc39.x86_64 37/153 Installing : libeconf-0.5.2-2.fc39.x86_64 38/153 Installing : systemd-libs-254.18-1.fc39.x86_64 39/153 Installing : mpfr-4.2.0-3.fc39.x86_64 40/153 Installing : dwz-0.15-3.fc39.x86_64 41/153 Installing : unzip-6.0-62.fc39.x86_64 42/153 Installing : file-libs-5.44-5.fc39.x86_64 43/153 Installing : file-5.44-5.fc39.x86_64 44/153 Installing : jansson-2.13.1-7.fc39.x86_64 45/153 Installing : libcap-ng-0.8.3-8.fc39.x86_64 46/153 Installing : audit-libs-3.1.5-1.fc39.x86_64 47/153 Installing : pam-libs-1.5.3-3.fc39.x86_64 48/153 Installing : libcom_err-1.47.0-2.fc39.x86_64 49/153 Installing : libsepol-3.5-2.fc39.x86_64 50/153 Installing : libtasn1-4.19.0-3.fc39.x86_64 51/153 Installing : libunistring-1.1-5.fc39.x86_64 52/153 Installing : libidn2-2.3.7-1.fc39.x86_64 53/153 Installing : lua-libs-5.4.6-3.fc39.x86_64 54/153 Installing : alternatives-1.26-1.fc39.x86_64 55/153 Installing : libsmartcols-2.39.4-1.fc39.x86_64 56/153 Installing : libpsl-0.21.2-4.fc39.x86_64 57/153 Installing : zip-3.0-39.fc39.x86_64 58/153 Installing : zstd-1.5.6-1.fc39.x86_64 59/153 Installing : libfdisk-2.39.4-1.fc39.x86_64 60/153 Installing : bzip2-1.0.8-16.fc39.x86_64 61/153 Installing : libxml2-2.10.4-3.fc39.x86_64 62/153 Installing : sqlite-libs-3.42.0-7.fc39.x86_64 63/153 Installing : ed-1.19-4.fc39.x86_64 64/153 Installing : elfutils-default-yama-scope-0.191-2.fc39.noarch 65/153 Running scriptlet: elfutils-default-yama-scope-0.191-2.fc39.noarch 65/153 Installing : cpio-2.14-4.fc39.x86_64 66/153 Installing : diffutils-3.10-3.fc39.x86_64 67/153 Installing : gdbm-libs-1:1.23-4.fc39.x86_64 68/153 Installing : cyrus-sasl-lib-2.1.28-11.fc39.x86_64 69/153 Installing : libbrotli-1.1.0-1.fc39.x86_64 70/153 Installing : libdb-5.3.28-56.fc39.x86_64 71/153 Installing : libffi-3.4.4-4.fc39.x86_64 72/153 Installing : p11-kit-0.25.5-1.fc39.x86_64 73/153 Installing : p11-kit-trust-0.25.5-1.fc39.x86_64 74/153 Running scriptlet: p11-kit-trust-0.25.5-1.fc39.x86_64 74/153 Installing : libpkgconf-1.9.5-2.fc39.x86_64 75/153 Installing : pkgconf-1.9.5-2.fc39.x86_64 76/153 Installing : libsigsegv-2.14-5.fc39.x86_64 77/153 Installing : gawk-5.2.2-2.fc39.x86_64 78/153 Installing : libtool-ltdl-2.4.7-7.fc39.x86_64 79/153 Installing : libverto-0.3.2-6.fc39.x86_64 80/153 Installing : keyutils-libs-1.6.3-1.fc39.x86_64 81/153 Installing : libgomp-13.3.1-3.fc39.x86_64 82/153 Installing : libnghttp2-1.55.1-5.fc39.x86_64 83/153 Installing : xxhash-libs-0.8.2-4.fc39.x86_64 84/153 Installing : libssh-config-0.10.6-2.fc39.noarch 85/153 Installing : coreutils-common-9.3-7.fc39.x86_64 86/153 Installing : ansible-srpm-macros-1-12.fc39.noarch 87/153 Installing : pkgconf-m4-1.9.5-2.fc39.noarch 88/153 Installing : pkgconf-pkg-config-1.9.5-2.fc39.x86_64 89/153 Installing : perl-srpm-macros-1-51.fc39.noarch 90/153 Installing : pcre2-syntax-10.42-1.fc39.2.noarch 91/153 Installing : pcre2-10.42-1.fc39.2.x86_64 92/153 Installing : libselinux-3.5-5.fc39.x86_64 93/153 Installing : sed-4.8-14.fc39.x86_64 94/153 Installing : grep-3.11-3.fc39.x86_64 95/153 Installing : findutils-1:4.9.0-6.fc39.x86_64 96/153 Installing : xz-5.4.4-1.fc39.x86_64 97/153 Installing : libmount-2.39.4-1.fc39.x86_64 98/153 Installing : util-linux-core-2.39.4-1.fc39.x86_64 99/153 Installing : openssl-libs-1:3.1.4-4.fc39.x86_64 100/153 Installing : coreutils-9.3-7.fc39.x86_64 101/153 Running scriptlet: ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noar 102/153 Installing : ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noar 102/153 Running scriptlet: ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noar 102/153 Installing : krb5-libs-1.21.3-1.fc39.x86_64 103/153 Installing : libtirpc-1.3.5-0.fc39.x86_64 104/153 Running scriptlet: authselect-libs-1.4.3-1.fc39.x86_64 105/153 Installing : authselect-libs-1.4.3-1.fc39.x86_64 105/153 Installing : gzip-1.12-6.fc39.x86_64 106/153 Installing : libarchive-3.7.1-2.fc39.x86_64 107/153 Installing : cracklib-2.9.11-2.fc39.x86_64 108/153 Installing : libpwquality-1.4.5-6.fc39.x86_64 109/153 Installing : authselect-1.4.3-1.fc39.x86_64 110/153 Installing : libnsl2-2.0.0-6.fc39.x86_64 111/153 Installing : pam-1.5.3-3.fc39.x86_64 112/153 Installing : libssh-0.10.6-2.fc39.x86_64 113/153 Installing : libevent-2.1.12-9.fc39.x86_64 114/153 Installing : openldap-2.6.7-1.fc39.x86_64 115/153 Installing : libcurl-8.2.1-5.fc39.x86_64 116/153 Installing : elfutils-libs-0.191-2.fc39.x86_64 117/153 Installing : elfutils-debuginfod-client-0.191-2.fc39.x86_64 118/153 Installing : binutils-gold-2.40-14.fc39.x86_64 119/153 Running scriptlet: binutils-gold-2.40-14.fc39.x86_64 119/153 Installing : binutils-2.40-14.fc39.x86_64 120/153 Running scriptlet: binutils-2.40-14.fc39.x86_64 120/153 Installing : elfutils-0.191-2.fc39.x86_64 121/153 Installing : gdb-minimal-15.1-1.fc39.x86_64 122/153 Installing : debugedit-5.0-12.fc39.x86_64 123/153 Installing : curl-8.2.1-5.fc39.x86_64 124/153 Installing : rpm-sequoia-1.7.0-1.fc39.x86_64 125/153 Installing : rpm-libs-4.19.1.1-1.fc39.x86_64 126/153 Running scriptlet: rpm-4.19.1.1-1.fc39.x86_64 127/153 Installing : rpm-4.19.1.1-1.fc39.x86_64 127/153 Installing : efi-srpm-macros-5-9.fc39.noarch 128/153 Installing : lua-srpm-macros-1-13.fc39.noarch 129/153 Installing : rpmautospec-rpm-macros-0.7.2-1.fc39.noarch 130/153 Installing : rpm-build-libs-4.19.1.1-1.fc39.x86_64 131/153 Installing : libsemanage-3.5-4.fc39.x86_64 132/153 Installing : shadow-utils-2:4.14.0-2.fc39.x86_64 133/153 Running scriptlet: libutempter-1.2.1-10.fc39.x86_64 134/153 Installing : libutempter-1.2.1-10.fc39.x86_64 134/153 Installing : patch-2.7.6-22.fc39.x86_64 135/153 Installing : tar-2:1.35-2.fc39.x86_64 136/153 Installing : package-notes-srpm-macros-0.5-9.fc39.noarch 137/153 Installing : openblas-srpm-macros-2-14.fc39.noarch 138/153 Installing : ocaml-srpm-macros-8-2.fc39.noarch 139/153 Installing : kernel-srpm-macros-1.0-20.fc39.noarch 140/153 Installing : gnat-srpm-macros-6-3.fc39.noarch 141/153 Installing : ghc-srpm-macros-1.6.1-2.fc39.noarch 142/153 Installing : fpc-srpm-macros-1.3-8.fc39.noarch 143/153 Installing : fonts-srpm-macros-1:2.0.5-12.fc39.noarch 144/153 Installing : forge-srpm-macros-0.3.1-1.fc39.noarch 145/153 Installing : go-srpm-macros-3.5.0-1.fc39.noarch 146/153 Installing : python-srpm-macros-3.12-8.fc39.noarch 147/153 Installing : redhat-rpm-config-266-1.fc39.noarch 148/153 Installing : rpm-build-4.19.1.1-1.fc39.x86_64 149/153 Installing : pyproject-srpm-macros-1.15.1-1.fc39.noarch 150/153 Installing : util-linux-2.39.4-1.fc39.x86_64 151/153 Running scriptlet: util-linux-2.39.4-1.fc39.x86_64 151/153 Installing : which-2.21-40.fc39.x86_64 152/153 Installing : info-7.0.3-3.fc39.x86_64 153/153 Running scriptlet: filesystem-3.18-6.fc39.x86_64 153/153 Running scriptlet: ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noar 153/153 Running scriptlet: authselect-libs-1.4.3-1.fc39.x86_64 153/153 Running scriptlet: rpm-4.19.1.1-1.fc39.x86_64 153/153 Running scriptlet: info-7.0.3-3.fc39.x86_64 153/153 Verifying : authselect-1.4.3-1.fc39.x86_64 1/153 Verifying : authselect-libs-1.4.3-1.fc39.x86_64 2/153 Verifying : basesystem-11-18.fc39.noarch 3/153 Verifying : bzip2-1.0.8-16.fc39.x86_64 4/153 Verifying : bzip2-libs-1.0.8-16.fc39.x86_64 5/153 Verifying : cpio-2.14-4.fc39.x86_64 6/153 Verifying : cracklib-2.9.11-2.fc39.x86_64 7/153 Verifying : cyrus-sasl-lib-2.1.28-11.fc39.x86_64 8/153 Verifying : diffutils-3.10-3.fc39.x86_64 9/153 Verifying : dwz-0.15-3.fc39.x86_64 10/153 Verifying : ed-1.19-4.fc39.x86_64 11/153 Verifying : efi-srpm-macros-5-9.fc39.noarch 12/153 Verifying : file-5.44-5.fc39.x86_64 13/153 Verifying : file-libs-5.44-5.fc39.x86_64 14/153 Verifying : filesystem-3.18-6.fc39.x86_64 15/153 Verifying : fonts-srpm-macros-1:2.0.5-12.fc39.noarch 16/153 Verifying : fpc-srpm-macros-1.3-8.fc39.noarch 17/153 Verifying : gawk-5.2.2-2.fc39.x86_64 18/153 Verifying : gdbm-libs-1:1.23-4.fc39.x86_64 19/153 Verifying : ghc-srpm-macros-1.6.1-2.fc39.noarch 20/153 Verifying : gmp-1:6.2.1-5.fc39.x86_64 21/153 Verifying : gnat-srpm-macros-6-3.fc39.noarch 22/153 Verifying : grep-3.11-3.fc39.x86_64 23/153 Verifying : gzip-1.12-6.fc39.x86_64 24/153 Verifying : info-7.0.3-3.fc39.x86_64 25/153 Verifying : jansson-2.13.1-7.fc39.x86_64 26/153 Verifying : kernel-srpm-macros-1.0-20.fc39.noarch 27/153 Verifying : libattr-2.5.1-8.fc39.x86_64 28/153 Verifying : libbrotli-1.1.0-1.fc39.x86_64 29/153 Verifying : libcap-ng-0.8.3-8.fc39.x86_64 30/153 Verifying : libcom_err-1.47.0-2.fc39.x86_64 31/153 Verifying : libdb-5.3.28-56.fc39.x86_64 32/153 Verifying : libevent-2.1.12-9.fc39.x86_64 33/153 Verifying : libffi-3.4.4-4.fc39.x86_64 34/153 Verifying : libnsl2-2.0.0-6.fc39.x86_64 35/153 Verifying : libpkgconf-1.9.5-2.fc39.x86_64 36/153 Verifying : libpsl-0.21.2-4.fc39.x86_64 37/153 Verifying : libpwquality-1.4.5-6.fc39.x86_64 38/153 Verifying : libselinux-3.5-5.fc39.x86_64 39/153 Verifying : libsemanage-3.5-4.fc39.x86_64 40/153 Verifying : libsepol-3.5-2.fc39.x86_64 41/153 Verifying : libsigsegv-2.14-5.fc39.x86_64 42/153 Verifying : libtasn1-4.19.0-3.fc39.x86_64 43/153 Verifying : libtool-ltdl-2.4.7-7.fc39.x86_64 44/153 Verifying : libunistring-1.1-5.fc39.x86_64 45/153 Verifying : libutempter-1.2.1-10.fc39.x86_64 46/153 Verifying : libverto-0.3.2-6.fc39.x86_64 47/153 Verifying : libxcrypt-4.4.36-2.fc39.x86_64 48/153 Verifying : libxml2-2.10.4-3.fc39.x86_64 49/153 Verifying : lua-libs-5.4.6-3.fc39.x86_64 50/153 Verifying : lz4-libs-1.9.4-4.fc39.x86_64 51/153 Verifying : mpfr-4.2.0-3.fc39.x86_64 52/153 Verifying : ocaml-srpm-macros-8-2.fc39.noarch 53/153 Verifying : openblas-srpm-macros-2-14.fc39.noarch 54/153 Verifying : package-notes-srpm-macros-0.5-9.fc39.noarch 55/153 Verifying : patch-2.7.6-22.fc39.x86_64 56/153 Verifying : pcre2-10.42-1.fc39.2.x86_64 57/153 Verifying : pcre2-syntax-10.42-1.fc39.2.noarch 58/153 Verifying : perl-srpm-macros-1-51.fc39.noarch 59/153 Verifying : pkgconf-1.9.5-2.fc39.x86_64 60/153 Verifying : pkgconf-m4-1.9.5-2.fc39.noarch 61/153 Verifying : pkgconf-pkg-config-1.9.5-2.fc39.x86_64 62/153 Verifying : popt-1.19-3.fc39.x86_64 63/153 Verifying : sed-4.8-14.fc39.x86_64 64/153 Verifying : setup-2.14.4-1.fc39.noarch 65/153 Verifying : sqlite-libs-3.42.0-7.fc39.x86_64 66/153 Verifying : tar-2:1.35-2.fc39.x86_64 67/153 Verifying : unzip-6.0-62.fc39.x86_64 68/153 Verifying : which-2.21-40.fc39.x86_64 69/153 Verifying : xz-5.4.4-1.fc39.x86_64 70/153 Verifying : xz-libs-5.4.4-1.fc39.x86_64 71/153 Verifying : zip-3.0-39.fc39.x86_64 72/153 Verifying : zlib-1.2.13-4.fc39.x86_64 73/153 Verifying : alternatives-1.26-1.fc39.x86_64 74/153 Verifying : ansible-srpm-macros-1-12.fc39.noarch 75/153 Verifying : audit-libs-3.1.5-1.fc39.x86_64 76/153 Verifying : bash-5.2.26-1.fc39.x86_64 77/153 Verifying : binutils-2.40-14.fc39.x86_64 78/153 Verifying : binutils-gold-2.40-14.fc39.x86_64 79/153 Verifying : ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noar 80/153 Verifying : coreutils-9.3-7.fc39.x86_64 81/153 Verifying : coreutils-common-9.3-7.fc39.x86_64 82/153 Verifying : crypto-policies-20231204-1.git1e3a2e4.fc39.noarc 83/153 Verifying : curl-8.2.1-5.fc39.x86_64 84/153 Verifying : debugedit-5.0-12.fc39.x86_64 85/153 Verifying : elfutils-0.191-2.fc39.x86_64 86/153 Verifying : elfutils-debuginfod-client-0.191-2.fc39.x86_64 87/153 Verifying : elfutils-default-yama-scope-0.191-2.fc39.noarch 88/153 Verifying : elfutils-libelf-0.191-2.fc39.x86_64 89/153 Verifying : elfutils-libs-0.191-2.fc39.x86_64 90/153 Verifying : fedora-gpg-keys-39-2.noarch 91/153 Verifying : fedora-release-39-36.noarch 92/153 Verifying : fedora-release-common-39-36.noarch 93/153 Verifying : fedora-release-identity-basic-39-36.noarch 94/153 Verifying : fedora-repos-39-2.noarch 95/153 Verifying : findutils-1:4.9.0-6.fc39.x86_64 96/153 Verifying : forge-srpm-macros-0.3.1-1.fc39.noarch 97/153 Verifying : gdb-minimal-15.1-1.fc39.x86_64 98/153 Verifying : glibc-2.38-18.fc39.x86_64 99/153 Verifying : glibc-common-2.38-18.fc39.x86_64 100/153 Verifying : glibc-gconv-extra-2.38-18.fc39.x86_64 101/153 Verifying : glibc-minimal-langpack-2.38-18.fc39.x86_64 102/153 Verifying : go-srpm-macros-3.5.0-1.fc39.noarch 103/153 Verifying : keyutils-libs-1.6.3-1.fc39.x86_64 104/153 Verifying : krb5-libs-1.21.3-1.fc39.x86_64 105/153 Verifying : libacl-2.3.1-9.fc39.x86_64 106/153 Verifying : libarchive-3.7.1-2.fc39.x86_64 107/153 Verifying : libblkid-2.39.4-1.fc39.x86_64 108/153 Verifying : libcap-2.48-9.fc39.x86_64 109/153 Verifying : libcurl-8.2.1-5.fc39.x86_64 110/153 Verifying : libeconf-0.5.2-2.fc39.x86_64 111/153 Verifying : libfdisk-2.39.4-1.fc39.x86_64 112/153 Verifying : libgcc-13.3.1-3.fc39.x86_64 113/153 Verifying : libgomp-13.3.1-3.fc39.x86_64 114/153 Verifying : libidn2-2.3.7-1.fc39.x86_64 115/153 Verifying : libmount-2.39.4-1.fc39.x86_64 116/153 Verifying : libnghttp2-1.55.1-5.fc39.x86_64 117/153 Verifying : libsmartcols-2.39.4-1.fc39.x86_64 118/153 Verifying : libssh-0.10.6-2.fc39.x86_64 119/153 Verifying : libssh-config-0.10.6-2.fc39.noarch 120/153 Verifying : libstdc++-13.3.1-3.fc39.x86_64 121/153 Verifying : libtirpc-1.3.5-0.fc39.x86_64 122/153 Verifying : libuuid-2.39.4-1.fc39.x86_64 123/153 Verifying : libzstd-1.5.6-1.fc39.x86_64 124/153 Verifying : lua-srpm-macros-1-13.fc39.noarch 125/153 Verifying : ncurses-base-6.4-7.20230520.fc39.1.noarch 126/153 Verifying : ncurses-libs-6.4-7.20230520.fc39.1.x86_64 127/153 Verifying : openldap-2.6.7-1.fc39.x86_64 128/153 Verifying : openssl-libs-1:3.1.4-4.fc39.x86_64 129/153 Verifying : p11-kit-0.25.5-1.fc39.x86_64 130/153 Verifying : p11-kit-trust-0.25.5-1.fc39.x86_64 131/153 Verifying : pam-1.5.3-3.fc39.x86_64 132/153 Verifying : pam-libs-1.5.3-3.fc39.x86_64 133/153 Verifying : publicsuffix-list-dafsa-20240107-1.fc39.noarch 134/153 Verifying : pyproject-srpm-macros-1.15.1-1.fc39.noarch 135/153 Verifying : python-srpm-macros-3.12-8.fc39.noarch 136/153 Verifying : qt5-srpm-macros-5.15.14-2.fc39.noarch 137/153 Verifying : qt6-srpm-macros-6.6.2-1.fc39.noarch 138/153 Verifying : readline-8.2-6.fc39.x86_64 139/153 Verifying : redhat-rpm-config-266-1.fc39.noarch 140/153 Verifying : rpm-4.19.1.1-1.fc39.x86_64 141/153 Verifying : rpm-build-4.19.1.1-1.fc39.x86_64 142/153 Verifying : rpm-build-libs-4.19.1.1-1.fc39.x86_64 143/153 Verifying : rpm-libs-4.19.1.1-1.fc39.x86_64 144/153 Verifying : rpm-sequoia-1.7.0-1.fc39.x86_64 145/153 Verifying : rpmautospec-rpm-macros-0.7.2-1.fc39.noarch 146/153 Verifying : rust-srpm-macros-26.3-1.fc39.noarch 147/153 Verifying : shadow-utils-2:4.14.0-2.fc39.x86_64 148/153 Verifying : systemd-libs-254.18-1.fc39.x86_64 149/153 Verifying : util-linux-2.39.4-1.fc39.x86_64 150/153 Verifying : util-linux-core-2.39.4-1.fc39.x86_64 151/153 Verifying : xxhash-libs-0.8.2-4.fc39.x86_64 152/153 Verifying : zstd-1.5.6-1.fc39.x86_64 153/153 Installed: alternatives-1.26-1.fc39.x86_64 ansible-srpm-macros-1-12.fc39.noarch audit-libs-3.1.5-1.fc39.x86_64 authselect-1.4.3-1.fc39.x86_64 authselect-libs-1.4.3-1.fc39.x86_64 basesystem-11-18.fc39.noarch bash-5.2.26-1.fc39.x86_64 binutils-2.40-14.fc39.x86_64 binutils-gold-2.40-14.fc39.x86_64 bzip2-1.0.8-16.fc39.x86_64 bzip2-libs-1.0.8-16.fc39.x86_64 ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noarch coreutils-9.3-7.fc39.x86_64 coreutils-common-9.3-7.fc39.x86_64 cpio-2.14-4.fc39.x86_64 cracklib-2.9.11-2.fc39.x86_64 crypto-policies-20231204-1.git1e3a2e4.fc39.noarch curl-8.2.1-5.fc39.x86_64 cyrus-sasl-lib-2.1.28-11.fc39.x86_64 debugedit-5.0-12.fc39.x86_64 diffutils-3.10-3.fc39.x86_64 dwz-0.15-3.fc39.x86_64 ed-1.19-4.fc39.x86_64 efi-srpm-macros-5-9.fc39.noarch elfutils-0.191-2.fc39.x86_64 elfutils-debuginfod-client-0.191-2.fc39.x86_64 elfutils-default-yama-scope-0.191-2.fc39.noarch elfutils-libelf-0.191-2.fc39.x86_64 elfutils-libs-0.191-2.fc39.x86_64 fedora-gpg-keys-39-2.noarch fedora-release-39-36.noarch fedora-release-common-39-36.noarch fedora-release-identity-basic-39-36.noarch fedora-repos-39-2.noarch file-5.44-5.fc39.x86_64 file-libs-5.44-5.fc39.x86_64 filesystem-3.18-6.fc39.x86_64 findutils-1:4.9.0-6.fc39.x86_64 fonts-srpm-macros-1:2.0.5-12.fc39.noarch forge-srpm-macros-0.3.1-1.fc39.noarch fpc-srpm-macros-1.3-8.fc39.noarch gawk-5.2.2-2.fc39.x86_64 gdb-minimal-15.1-1.fc39.x86_64 gdbm-libs-1:1.23-4.fc39.x86_64 ghc-srpm-macros-1.6.1-2.fc39.noarch glibc-2.38-18.fc39.x86_64 glibc-common-2.38-18.fc39.x86_64 glibc-gconv-extra-2.38-18.fc39.x86_64 glibc-minimal-langpack-2.38-18.fc39.x86_64 gmp-1:6.2.1-5.fc39.x86_64 gnat-srpm-macros-6-3.fc39.noarch go-srpm-macros-3.5.0-1.fc39.noarch grep-3.11-3.fc39.x86_64 gzip-1.12-6.fc39.x86_64 info-7.0.3-3.fc39.x86_64 jansson-2.13.1-7.fc39.x86_64 kernel-srpm-macros-1.0-20.fc39.noarch keyutils-libs-1.6.3-1.fc39.x86_64 krb5-libs-1.21.3-1.fc39.x86_64 libacl-2.3.1-9.fc39.x86_64 libarchive-3.7.1-2.fc39.x86_64 libattr-2.5.1-8.fc39.x86_64 libblkid-2.39.4-1.fc39.x86_64 libbrotli-1.1.0-1.fc39.x86_64 libcap-2.48-9.fc39.x86_64 libcap-ng-0.8.3-8.fc39.x86_64 libcom_err-1.47.0-2.fc39.x86_64 libcurl-8.2.1-5.fc39.x86_64 libdb-5.3.28-56.fc39.x86_64 libeconf-0.5.2-2.fc39.x86_64 libevent-2.1.12-9.fc39.x86_64 libfdisk-2.39.4-1.fc39.x86_64 libffi-3.4.4-4.fc39.x86_64 libgcc-13.3.1-3.fc39.x86_64 libgomp-13.3.1-3.fc39.x86_64 libidn2-2.3.7-1.fc39.x86_64 libmount-2.39.4-1.fc39.x86_64 libnghttp2-1.55.1-5.fc39.x86_64 libnsl2-2.0.0-6.fc39.x86_64 libpkgconf-1.9.5-2.fc39.x86_64 libpsl-0.21.2-4.fc39.x86_64 libpwquality-1.4.5-6.fc39.x86_64 libselinux-3.5-5.fc39.x86_64 libsemanage-3.5-4.fc39.x86_64 libsepol-3.5-2.fc39.x86_64 libsigsegv-2.14-5.fc39.x86_64 libsmartcols-2.39.4-1.fc39.x86_64 libssh-0.10.6-2.fc39.x86_64 libssh-config-0.10.6-2.fc39.noarch libstdc++-13.3.1-3.fc39.x86_64 libtasn1-4.19.0-3.fc39.x86_64 libtirpc-1.3.5-0.fc39.x86_64 libtool-ltdl-2.4.7-7.fc39.x86_64 libunistring-1.1-5.fc39.x86_64 libutempter-1.2.1-10.fc39.x86_64 libuuid-2.39.4-1.fc39.x86_64 libverto-0.3.2-6.fc39.x86_64 libxcrypt-4.4.36-2.fc39.x86_64 libxml2-2.10.4-3.fc39.x86_64 libzstd-1.5.6-1.fc39.x86_64 lua-libs-5.4.6-3.fc39.x86_64 lua-srpm-macros-1-13.fc39.noarch lz4-libs-1.9.4-4.fc39.x86_64 mpfr-4.2.0-3.fc39.x86_64 ncurses-base-6.4-7.20230520.fc39.1.noarch ncurses-libs-6.4-7.20230520.fc39.1.x86_64 ocaml-srpm-macros-8-2.fc39.noarch openblas-srpm-macros-2-14.fc39.noarch openldap-2.6.7-1.fc39.x86_64 openssl-libs-1:3.1.4-4.fc39.x86_64 p11-kit-0.25.5-1.fc39.x86_64 p11-kit-trust-0.25.5-1.fc39.x86_64 package-notes-srpm-macros-0.5-9.fc39.noarch pam-1.5.3-3.fc39.x86_64 pam-libs-1.5.3-3.fc39.x86_64 patch-2.7.6-22.fc39.x86_64 pcre2-10.42-1.fc39.2.x86_64 pcre2-syntax-10.42-1.fc39.2.noarch perl-srpm-macros-1-51.fc39.noarch pkgconf-1.9.5-2.fc39.x86_64 pkgconf-m4-1.9.5-2.fc39.noarch pkgconf-pkg-config-1.9.5-2.fc39.x86_64 popt-1.19-3.fc39.x86_64 publicsuffix-list-dafsa-20240107-1.fc39.noarch pyproject-srpm-macros-1.15.1-1.fc39.noarch python-srpm-macros-3.12-8.fc39.noarch qt5-srpm-macros-5.15.14-2.fc39.noarch qt6-srpm-macros-6.6.2-1.fc39.noarch readline-8.2-6.fc39.x86_64 redhat-rpm-config-266-1.fc39.noarch rpm-4.19.1.1-1.fc39.x86_64 rpm-build-4.19.1.1-1.fc39.x86_64 rpm-build-libs-4.19.1.1-1.fc39.x86_64 rpm-libs-4.19.1.1-1.fc39.x86_64 rpm-sequoia-1.7.0-1.fc39.x86_64 rpmautospec-rpm-macros-0.7.2-1.fc39.noarch rust-srpm-macros-26.3-1.fc39.noarch sed-4.8-14.fc39.x86_64 setup-2.14.4-1.fc39.noarch shadow-utils-2:4.14.0-2.fc39.x86_64 sqlite-libs-3.42.0-7.fc39.x86_64 systemd-libs-254.18-1.fc39.x86_64 tar-2:1.35-2.fc39.x86_64 unzip-6.0-62.fc39.x86_64 util-linux-2.39.4-1.fc39.x86_64 util-linux-core-2.39.4-1.fc39.x86_64 which-2.21-40.fc39.x86_64 xxhash-libs-0.8.2-4.fc39.x86_64 xz-5.4.4-1.fc39.x86_64 xz-libs-5.4.4-1.fc39.x86_64 zip-3.0-39.fc39.x86_64 zlib-1.2.13-4.fc39.x86_64 zstd-1.5.6-1.fc39.x86_64 Complete! Finish: installing minimal buildroot with dnf Start: creating root cache Finish: creating root cache Finish: chroot init INFO: Installed packages: INFO: alternatives-1.26-1.fc39.x86_64 ansible-srpm-macros-1-12.fc39.noarch audit-libs-3.1.5-1.fc39.x86_64 authselect-1.4.3-1.fc39.x86_64 authselect-libs-1.4.3-1.fc39.x86_64 basesystem-11-18.fc39.noarch bash-5.2.26-1.fc39.x86_64 binutils-2.40-14.fc39.x86_64 binutils-gold-2.40-14.fc39.x86_64 bzip2-1.0.8-16.fc39.x86_64 bzip2-libs-1.0.8-16.fc39.x86_64 ca-certificates-2024.2.69_v8.0.401-1.0.fc39.noarch coreutils-9.3-7.fc39.x86_64 coreutils-common-9.3-7.fc39.x86_64 cpio-2.14-4.fc39.x86_64 cracklib-2.9.11-2.fc39.x86_64 crypto-policies-20231204-1.git1e3a2e4.fc39.noarch curl-8.2.1-5.fc39.x86_64 cyrus-sasl-lib-2.1.28-11.fc39.x86_64 debugedit-5.0-12.fc39.x86_64 diffutils-3.10-3.fc39.x86_64 dwz-0.15-3.fc39.x86_64 ed-1.19-4.fc39.x86_64 efi-srpm-macros-5-9.fc39.noarch elfutils-0.191-2.fc39.x86_64 elfutils-debuginfod-client-0.191-2.fc39.x86_64 elfutils-default-yama-scope-0.191-2.fc39.noarch elfutils-libelf-0.191-2.fc39.x86_64 elfutils-libs-0.191-2.fc39.x86_64 fedora-gpg-keys-39-2.noarch fedora-release-39-36.noarch fedora-release-common-39-36.noarch fedora-release-identity-basic-39-36.noarch fedora-repos-39-2.noarch file-5.44-5.fc39.x86_64 file-libs-5.44-5.fc39.x86_64 filesystem-3.18-6.fc39.x86_64 findutils-4.9.0-6.fc39.x86_64 fonts-srpm-macros-2.0.5-12.fc39.noarch forge-srpm-macros-0.3.1-1.fc39.noarch fpc-srpm-macros-1.3-8.fc39.noarch gawk-5.2.2-2.fc39.x86_64 gdb-minimal-15.1-1.fc39.x86_64 gdbm-libs-1.23-4.fc39.x86_64 ghc-srpm-macros-1.6.1-2.fc39.noarch glibc-2.38-18.fc39.x86_64 glibc-common-2.38-18.fc39.x86_64 glibc-gconv-extra-2.38-18.fc39.x86_64 glibc-minimal-langpack-2.38-18.fc39.x86_64 gmp-6.2.1-5.fc39.x86_64 gnat-srpm-macros-6-3.fc39.noarch go-srpm-macros-3.5.0-1.fc39.noarch gpg-pubkey-18b8e74c-62f2920f grep-3.11-3.fc39.x86_64 gzip-1.12-6.fc39.x86_64 info-7.0.3-3.fc39.x86_64 jansson-2.13.1-7.fc39.x86_64 kernel-srpm-macros-1.0-20.fc39.noarch keyutils-libs-1.6.3-1.fc39.x86_64 krb5-libs-1.21.3-1.fc39.x86_64 libacl-2.3.1-9.fc39.x86_64 libarchive-3.7.1-2.fc39.x86_64 libattr-2.5.1-8.fc39.x86_64 libblkid-2.39.4-1.fc39.x86_64 libbrotli-1.1.0-1.fc39.x86_64 libcap-2.48-9.fc39.x86_64 libcap-ng-0.8.3-8.fc39.x86_64 libcom_err-1.47.0-2.fc39.x86_64 libcurl-8.2.1-5.fc39.x86_64 libdb-5.3.28-56.fc39.x86_64 libeconf-0.5.2-2.fc39.x86_64 libevent-2.1.12-9.fc39.x86_64 libfdisk-2.39.4-1.fc39.x86_64 libffi-3.4.4-4.fc39.x86_64 libgcc-13.3.1-3.fc39.x86_64 libgomp-13.3.1-3.fc39.x86_64 libidn2-2.3.7-1.fc39.x86_64 libmount-2.39.4-1.fc39.x86_64 libnghttp2-1.55.1-5.fc39.x86_64 libnsl2-2.0.0-6.fc39.x86_64 libpkgconf-1.9.5-2.fc39.x86_64 libpsl-0.21.2-4.fc39.x86_64 libpwquality-1.4.5-6.fc39.x86_64 libselinux-3.5-5.fc39.x86_64 libsemanage-3.5-4.fc39.x86_64 libsepol-3.5-2.fc39.x86_64 libsigsegv-2.14-5.fc39.x86_64 libsmartcols-2.39.4-1.fc39.x86_64 libssh-0.10.6-2.fc39.x86_64 libssh-config-0.10.6-2.fc39.noarch libstdc++-13.3.1-3.fc39.x86_64 libtasn1-4.19.0-3.fc39.x86_64 libtirpc-1.3.5-0.fc39.x86_64 libtool-ltdl-2.4.7-7.fc39.x86_64 libunistring-1.1-5.fc39.x86_64 libutempter-1.2.1-10.fc39.x86_64 libuuid-2.39.4-1.fc39.x86_64 libverto-0.3.2-6.fc39.x86_64 libxcrypt-4.4.36-2.fc39.x86_64 libxml2-2.10.4-3.fc39.x86_64 libzstd-1.5.6-1.fc39.x86_64 lua-libs-5.4.6-3.fc39.x86_64 lua-srpm-macros-1-13.fc39.noarch lz4-libs-1.9.4-4.fc39.x86_64 mpfr-4.2.0-3.fc39.x86_64 ncurses-base-6.4-7.20230520.fc39.1.noarch ncurses-libs-6.4-7.20230520.fc39.1.x86_64 ocaml-srpm-macros-8-2.fc39.noarch openblas-srpm-macros-2-14.fc39.noarch openldap-2.6.7-1.fc39.x86_64 openssl-libs-3.1.4-4.fc39.x86_64 p11-kit-0.25.5-1.fc39.x86_64 p11-kit-trust-0.25.5-1.fc39.x86_64 package-notes-srpm-macros-0.5-9.fc39.noarch pam-1.5.3-3.fc39.x86_64 pam-libs-1.5.3-3.fc39.x86_64 patch-2.7.6-22.fc39.x86_64 pcre2-10.42-1.fc39.2.x86_64 pcre2-syntax-10.42-1.fc39.2.noarch perl-srpm-macros-1-51.fc39.noarch pkgconf-1.9.5-2.fc39.x86_64 pkgconf-m4-1.9.5-2.fc39.noarch pkgconf-pkg-config-1.9.5-2.fc39.x86_64 popt-1.19-3.fc39.x86_64 publicsuffix-list-dafsa-20240107-1.fc39.noarch pyproject-srpm-macros-1.15.1-1.fc39.noarch python-srpm-macros-3.12-8.fc39.noarch qt5-srpm-macros-5.15.14-2.fc39.noarch qt6-srpm-macros-6.6.2-1.fc39.noarch readline-8.2-6.fc39.x86_64 redhat-rpm-config-266-1.fc39.noarch rpm-4.19.1.1-1.fc39.x86_64 rpm-build-4.19.1.1-1.fc39.x86_64 rpm-build-libs-4.19.1.1-1.fc39.x86_64 rpm-libs-4.19.1.1-1.fc39.x86_64 rpm-sequoia-1.7.0-1.fc39.x86_64 rpmautospec-rpm-macros-0.7.2-1.fc39.noarch rust-srpm-macros-26.3-1.fc39.noarch sed-4.8-14.fc39.x86_64 setup-2.14.4-1.fc39.noarch shadow-utils-4.14.0-2.fc39.x86_64 sqlite-libs-3.42.0-7.fc39.x86_64 systemd-libs-254.18-1.fc39.x86_64 tar-1.35-2.fc39.x86_64 unzip-6.0-62.fc39.x86_64 util-linux-2.39.4-1.fc39.x86_64 util-linux-core-2.39.4-1.fc39.x86_64 which-2.21-40.fc39.x86_64 xxhash-libs-0.8.2-4.fc39.x86_64 xz-5.4.4-1.fc39.x86_64 xz-libs-5.4.4-1.fc39.x86_64 zip-3.0-39.fc39.x86_64 zlib-1.2.13-4.fc39.x86_64 zstd-1.5.6-1.fc39.x86_64 Start: buildsrpm Start: rpmbuild -bs warning: source_date_epoch_from_changelog set but %changelog is missing Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/zapzap-5.3.8-1.fc39.src.rpm RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing Finish: rpmbuild -bs INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-39-x86_64-1729951987.459697/root/var/log/dnf.log /var/lib/mock/fedora-39-x86_64-1729951987.459697/root/var/log/dnf.librepo.log /var/lib/mock/fedora-39-x86_64-1729951987.459697/root/var/log/dnf.rpm.log Finish: buildsrpm INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-gbzu_9r0/zapzap/zapzap.spec) Config(child) 1 minutes 56 seconds INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results INFO: Cleaning up build root ('cleanup_on_success=True') Start: clean chroot INFO: unmounting tmpfs. Finish: clean chroot INFO: Start(/var/lib/copr-rpmbuild/results/zapzap-5.3.8-1.fc39.src.rpm) Config(fedora-39-x86_64) Start(bootstrap): chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-39-x86_64-bootstrap-1729951987.459697/root. INFO: reusing tmpfs at /var/lib/mock/fedora-39-x86_64-bootstrap-1729951987.459697/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata Finish(bootstrap): chroot init Start: chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-39-x86_64-1729951987.459697/root. INFO: calling preinit hooks INFO: enabled root cache Start: unpacking root cache Finish: unpacking root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin INFO: Buildroot is handled by package management downloaded with a bootstrap image: rpm-4.19.1.1-1.fc39.x86_64 rpm-sequoia-1.7.0-1.fc39.x86_64 python3-dnf-4.21.1-1.fc39.noarch python3-dnf-plugins-core-4.9.0-1.fc39.noarch yum-4.21.1-1.fc39.noarch Finish: chroot init Start: build phase for zapzap-5.3.8-1.fc39.src.rpm Start: build setup for zapzap-5.3.8-1.fc39.src.rpm warning: source_date_epoch_from_changelog set but %changelog is missing Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/zapzap-5.3.8-1.fc39.src.rpm RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 27 kB/s | 1.8 kB 00:00 fedora 1.1 MB/s | 30 kB 00:00 updates 1.0 MB/s | 27 kB 00:00 Dependencies resolved. ================================================================================ Package Arch Version Repo Size ================================================================================ Installing: desktop-file-utils x86_64 0.26-9.fc39 fedora 72 k python3-devel x86_64 3.12.7-1.fc39 updates 314 k python3-pyqt6 x86_64 6.6.1-5.fc39 updates 1.1 M python3-setuptools noarch 67.7.2-8.fc39 updates 1.5 M Installing dependencies: SDL2 x86_64 2.28.5-1.fc39 updates 692 k abattis-cantarell-vf-fonts noarch 0.301-10.fc39 fedora 121 k adwaita-cursor-theme noarch 45.0-1.fc39 fedora 678 k adwaita-icon-theme noarch 45.0-1.fc39 fedora 407 k alsa-lib x86_64 1.2.12-1.fc39 updates 521 k at-spi2-atk x86_64 2.50.2-1.fc39 updates 86 k at-spi2-core x86_64 2.50.2-1.fc39 updates 371 k atk x86_64 2.50.2-1.fc39 updates 81 k avahi-libs x86_64 0.8-24.fc39 fedora 67 k bluez-libs x86_64 5.77-1.fc39 updates 85 k cairo x86_64 1.18.0-1.fc39 fedora 710 k cairo-gobject x86_64 1.18.0-1.fc39 fedora 19 k cdparanoia-libs x86_64 10.2-42.fc39 fedora 54 k cjson x86_64 1.7.17-1.fc39 updates 32 k codec2 x86_64 1.2.0-2.fc39 fedora 638 k colord-libs x86_64 1.4.6-6.fc39 fedora 233 k cups-libs x86_64 1:2.4.10-7.fc39 updates 268 k dbus x86_64 1:1.14.10-1.fc39 fedora 8.1 k dbus-broker x86_64 36-2.fc39 updates 176 k dbus-common noarch 1:1.14.10-1.fc39 fedora 15 k dbus-libs x86_64 1:1.14.10-1.fc39 fedora 156 k default-fonts-core-sans noarch 4.0-9.fc39 fedora 32 k double-conversion x86_64 3.1.5-9.fc39 fedora 49 k duktape x86_64 2.7.0-5.fc39 fedora 170 k emacs-filesystem noarch 1:29.4-2.fc39 updates 7.3 k expat x86_64 2.6.3-1.fc39 updates 114 k fdk-aac-free x86_64 2.0.0-11.fc39 fedora 336 k flac-libs x86_64 1.4.3-2.fc39 fedora 264 k fontconfig x86_64 2.14.2-6.fc39 updates 296 k fonts-filesystem noarch 1:2.0.5-12.fc39 fedora 8.2 k freetype x86_64 2.13.1-2.fc39 fedora 414 k fribidi x86_64 1.0.13-2.fc39 fedora 91 k game-music-emu x86_64 0.6.3-12.fc39 fedora 156 k gdk-pixbuf2 x86_64 2.42.10-5.fc39 fedora 484 k gdk-pixbuf2-modules x86_64 2.42.10-5.fc39 fedora 85 k glib2 x86_64 2.78.6-1.fc39 updates 2.8 M glx-utils x86_64 9.0.0-3.fc39 fedora 77 k gnutls x86_64 3.8.6-1.fc39 updates 1.1 M google-noto-fonts-common noarch 20240101-1.fc39 updates 17 k google-noto-sans-vf-fonts noarch 20240101-1.fc39 updates 593 k graphene x86_64 1.10.6-6.fc39 fedora 61 k graphite2 x86_64 1.3.14-12.fc39 fedora 95 k gsm x86_64 1.0.22-3.fc39 fedora 35 k gssdp x86_64 1.6.3-1.fc39 updates 58 k gstreamer1 x86_64 1.22.12-1.fc39 updates 1.4 M gstreamer1-plugins-bad-free-libs x86_64 1.22.12-1.fc39 updates 767 k gstreamer1-plugins-base x86_64 1.22.12-1.fc39 updates 2.2 M gtk-update-icon-cache x86_64 3.24.43-1.fc39 updates 34 k gtk3 x86_64 3.24.43-1.fc39 updates 5.6 M gupnp x86_64 1.6.6-1.fc39 updates 107 k gupnp-igd x86_64 1.6.0-2.fc39 fedora 34 k harfbuzz x86_64 8.2.1-2.fc39 fedora 975 k hicolor-icon-theme noarch 0.17-16.fc39 fedora 66 k highway x86_64 1.1.0-1.fc39 updates 496 k hwdata noarch 0.388-1.fc39 updates 1.6 M ilbc x86_64 3.0.4-7.fc39 fedora 53 k iso-codes noarch 4.15.0-2.fc39 fedora 3.5 M jbigkit-libs x86_64 2.1-26.fc39 fedora 53 k json-glib x86_64 1.8.0-1.fc39 fedora 166 k kmod-libs x86_64 30-6.fc39 fedora 67 k lame-libs x86_64 3.100-15.fc39 fedora 337 k lcms2 x86_64 2.15-2.fc39 fedora 177 k libICE x86_64 1.0.10-11.fc39 fedora 70 k libSM x86_64 1.2.3-13.fc39 fedora 41 k libX11 x86_64 1.8.9-1.fc39 updates 650 k libX11-common noarch 1.8.9-1.fc39 updates 176 k libX11-xcb x86_64 1.8.9-1.fc39 updates 12 k libXau x86_64 1.0.11-3.fc39 fedora 31 k libXcomposite x86_64 0.4.5-10.fc39 fedora 23 k libXcursor x86_64 1.2.1-4.fc39 fedora 30 k libXdamage x86_64 1.1.5-10.fc39 fedora 22 k libXext x86_64 1.3.5-3.fc39 fedora 39 k libXfixes x86_64 6.0.0-6.fc39 fedora 19 k libXft x86_64 2.3.8-3.fc39 fedora 72 k libXi x86_64 1.8.1-2.fc39 fedora 40 k libXinerama x86_64 1.1.5-3.fc39 fedora 14 k libXrandr x86_64 1.5.4-1.fc39 updates 27 k libXrender x86_64 0.9.11-3.fc39 fedora 27 k libXtst x86_64 1.2.4-3.fc39 fedora 20 k libXv x86_64 1.0.11-19.fc39 fedora 18 k libXxf86vm x86_64 1.1.5-3.fc39 fedora 18 k libaom x86_64 3.9.0-1.fc39 updates 1.8 M libasyncns x86_64 0.8-25.fc39 fedora 30 k libavcodec-free x86_64 6.1.2-1.fc39 updates 4.1 M libavformat-free x86_64 6.1.2-1.fc39 updates 1.1 M libavutil-free x86_64 6.1.2-1.fc39 updates 354 k libb2 x86_64 0.98.1-9.fc39 fedora 25 k libbluray x86_64 1.3.4-3.fc39 fedora 172 k libchromaprint x86_64 1.5.1-13.fc39 fedora 40 k libcloudproviders x86_64 0.3.5-1.fc39 updates 46 k libdatrie x86_64 0.2.13-7.fc39 fedora 32 k libdav1d x86_64 1.2.1-2.fc39 fedora 618 k libdecor x86_64 0.2.2-1.fc39 updates 59 k libdrm x86_64 2.4.121-1.fc39 updates 157 k libepoxy x86_64 1.5.10-4.fc39 fedora 234 k libevdev x86_64 1.13.1-2.fc39 fedora 44 k libgcrypt x86_64 1.10.2-2.fc39 fedora 507 k libglvnd x86_64 1:1.7.0-1.fc39 fedora 133 k libglvnd-egl x86_64 1:1.7.0-1.fc39 fedora 36 k libglvnd-glx x86_64 1:1.7.0-1.fc39 fedora 142 k libglvnd-opengl x86_64 1:1.7.0-1.fc39 fedora 42 k libgpg-error x86_64 1.47-2.fc39 fedora 230 k libgudev x86_64 238-2.fc39 fedora 35 k libgusb x86_64 0.4.9-1.fc39 updates 65 k libicu x86_64 73.2-2.fc39 fedora 11 M libinput x86_64 1.25.0-5.fc39 updates 215 k libjpeg-turbo x86_64 2.1.4-3.fc39 fedora 183 k libjxl x86_64 1:0.8.3-1.fc39 updates 1.2 M libldb x86_64 2.8.1-1.fc39 updates 181 k liblerc x86_64 4.0.0-4.fc39 fedora 201 k libmodplug x86_64 1:0.8.9.0-17.fc39 fedora 176 k libnice x86_64 0.1.21-4.fc39 fedora 200 k libogg x86_64 2:1.3.5-6.fc39 fedora 33 k libopenmpt x86_64 0.7.8-1.fc39 updates 686 k libpciaccess x86_64 0.16-9.fc39 fedora 26 k libpng x86_64 2:1.6.37-15.fc39 fedora 119 k libproxy x86_64 0.5.5-1.fc39 updates 48 k librabbitmq x86_64 0.13.0-3.fc39 fedora 43 k librist x86_64 0.2.7-2.fc39 fedora 77 k librsvg2 x86_64 2.57.1-2.fc39 updates 1.6 M libseccomp x86_64 2.5.5-1.fc39 updates 70 k libsmbclient x86_64 2:4.19.8-1.fc39 updates 76 k libsndfile x86_64 1.1.0-9.fc39 fedora 215 k libsodium x86_64 1.0.18-15.fc39 updates 162 k libsoup3 x86_64 3.4.4-1.fc39 updates 389 k libstemmer x86_64 2.2.0-7.fc39 fedora 171 k libswresample-free x86_64 6.1.2-1.fc39 updates 67 k libswscale-free x86_64 6.1.2-1.fc39 updates 188 k libtalloc x86_64 2.4.1-1.fc39 fedora 30 k libtdb x86_64 1.4.9-1.fc39 fedora 51 k libtevent x86_64 0.15.0-1.fc39 fedora 45 k libthai x86_64 0.1.29-6.fc39 fedora 213 k libtheora x86_64 1:1.1.1-34.fc39 fedora 166 k libtiff x86_64 4.4.0-8.fc39 fedora 202 k libtracker-sparql x86_64 3.6.0-1.fc39 fedora 374 k libudfread x86_64 1.1.2-6.fc39 fedora 35 k libunwind x86_64 1.7.0-0.2.rc2.fc39 fedora 70 k libusb1 x86_64 1.0.27-2.fc39 updates 76 k libva x86_64 2.20.0-2.fc39 updates 107 k libvdpau x86_64 1.5-4.fc39 fedora 16 k libvisual x86_64 1:0.4.1-2.fc39 fedora 151 k libvmaf x86_64 2.3.0-6.fc39 fedora 180 k libvorbis x86_64 1:1.3.7-8.fc39 fedora 195 k libvpl x86_64 1:2.13.0-1.fc39 updates 154 k libvpx x86_64 1.13.1-1.fc39 updates 1.1 M libwacom x86_64 2.10.0-1.fc39 updates 43 k libwacom-data noarch 2.10.0-1.fc39 updates 196 k libwayland-client x86_64 1.22.0-2.fc39 fedora 34 k libwayland-cursor x86_64 1.22.0-2.fc39 fedora 19 k libwayland-egl x86_64 1.22.0-2.fc39 fedora 13 k libwayland-server x86_64 1.22.0-2.fc39 fedora 42 k libwbclient x86_64 2:4.19.8-1.fc39 updates 45 k libwebp x86_64 1.3.2-2.fc39 fedora 284 k libxcb x86_64 1.13.1-12.fc39 fedora 233 k libxkbcommon x86_64 1.6.0-1.fc39 updates 142 k libxkbcommon-x11 x86_64 1.6.0-1.fc39 updates 22 k libxshmfence x86_64 1.3-13.fc39 fedora 12 k lmdb-libs x86_64 0.9.33-1.fc39 updates 61 k lpcnetfreedv x86_64 0.5-3.fc39 fedora 7.3 M mbedtls x86_64 2.28.8-1.fc39 updates 403 k mesa-filesystem x86_64 23.3.6-1.fc39 updates 19 k mesa-libEGL x86_64 23.3.6-1.fc39 updates 134 k mesa-libGL x86_64 23.3.6-1.fc39 updates 176 k mesa-libgbm x86_64 23.3.6-1.fc39 updates 46 k mesa-libglapi x86_64 23.3.6-1.fc39 updates 53 k mpdecimal x86_64 2.5.1-7.fc39 fedora 89 k mpg123-libs x86_64 1.31.3-2.fc39 fedora 340 k mtdev x86_64 1.1.6-6.fc39 fedora 20 k nettle x86_64 3.9.1-2.fc39 fedora 425 k ocl-icd x86_64 2.3.2-2.fc39 fedora 67 k opencore-amr x86_64 0.1.6-4.fc39 fedora 177 k openjpeg2 x86_64 2.5.2-1.fc39 updates 178 k openpgm x86_64 5.2.122-32.fc39 fedora 176 k opus x86_64 1.3.1-13.fc39 fedora 205 k orc x86_64 0.4.33-3.fc39 fedora 202 k pango x86_64 1.51.0-1.fc39 fedora 343 k pcre2-utf16 x86_64 10.42-1.fc39.2 fedora 212 k pixman x86_64 0.42.2-2.fc39 fedora 288 k pulseaudio-libs x86_64 16.1-5.fc39 fedora 694 k pyproject-rpm-macros noarch 1.15.1-1.fc39 updates 43 k python-pip-wheel noarch 23.2.1-2.fc39 updates 1.5 M python-pyqt6-rpm-macros noarch 6.6.1-5.fc39 updates 9.4 k python-rpm-macros noarch 3.12-8.fc39 updates 18 k python3 x86_64 3.12.7-1.fc39 updates 28 k python3-dbus x86_64 1.3.2-4.fc39 fedora 157 k python3-libs x86_64 3.12.7-1.fc39 updates 9.2 M python3-packaging noarch 23.1-4.fc39 fedora 114 k python3-pyqt6-base x86_64 6.6.1-5.fc39 updates 3.3 M python3-pyqt6-sip x86_64 13.6.0-1.fc39 updates 77 k python3-rpm-generators noarch 14-7.fc39 fedora 30 k python3-rpm-macros noarch 3.12-8.fc39 updates 12 k qt6-qtbase x86_64 6.6.2-2.fc39 updates 3.9 M qt6-qtbase-common noarch 6.6.2-2.fc39 updates 11 k qt6-qtbase-gui x86_64 6.6.2-2.fc39 updates 7.3 M qt6-qtconnectivity x86_64 6.6.2-1.fc39 updates 470 k qt6-qtdeclarative x86_64 6.6.2-3.fc39 updates 9.6 M qt6-qtmultimedia x86_64 6.6.2-1.fc39 updates 1.0 M qt6-qtpdf x86_64 6.6.2-1.fc39 updates 2.4 M qt6-qtpositioning x86_64 6.6.2-1.fc39 updates 443 k qt6-qtquick3d x86_64 6.6.2-1.fc39 updates 4.1 M qt6-qtquicktimeline x86_64 6.6.2-1.fc39 updates 59 k qt6-qtremoteobjects x86_64 6.6.2-1.fc39 updates 475 k qt6-qtsensors x86_64 6.6.2-1.fc39 updates 226 k qt6-qtserialport x86_64 6.6.2-1.fc39 updates 76 k qt6-qtshadertools x86_64 6.6.2-1.fc39 updates 1.4 M qt6-qtspeech x86_64 6.6.2-1.fc39 updates 111 k qt6-qtsvg x86_64 6.6.2-1.fc39 updates 206 k qt6-qttools-common noarch 6.6.2-1.fc39 updates 11 k qt6-qttools-libs-designer x86_64 6.6.2-1.fc39 updates 2.9 M qt6-qttools-libs-help x86_64 6.6.2-1.fc39 updates 199 k qt6-qtwebchannel x86_64 6.6.2-1.fc39 updates 151 k qt6-qtwebsockets x86_64 6.6.2-1.fc39 updates 104 k rav1e-libs x86_64 0.7.1-4.fc39 updates 1.0 M rsvg-pixbuf-loader x86_64 2.57.1-2.fc39 updates 16 k samba-client-libs x86_64 2:4.19.8-1.fc39 updates 5.2 M samba-common noarch 2:4.19.8-1.fc39 updates 150 k samba-common-libs x86_64 2:4.19.8-1.fc39 updates 107 k shared-mime-info x86_64 2.2-4.fc39 fedora 380 k snappy x86_64 1.1.10-2.fc39 fedora 37 k soxr x86_64 0.1.3-14.fc39 fedora 84 k speex x86_64 1.2.0-15.fc39 fedora 67 k srt-libs x86_64 1.5.3-1.fc39 fedora 370 k svt-av1-libs x86_64 1.4.1-3.fc39 fedora 2.0 M systemd x86_64 254.18-1.fc39 updates 4.7 M systemd-pam x86_64 254.18-1.fc39 updates 357 k systemd-rpm-macros noarch 254.18-1.fc39 updates 25 k tslib x86_64 1.22-9.fc39 fedora 154 k twolame-libs x86_64 0.4.0-3.fc39 fedora 69 k tzdata noarch 2024a-2.fc39 updates 715 k vapoursynth-libs x86_64 63-2.fc39 fedora 567 k vo-amrwbenc x86_64 0.1.3-19.fc39 fedora 80 k vulkan-loader x86_64 1.3.275.0-1.fc39 updates 149 k xcb-util x86_64 0.4.1-3.fc39 fedora 18 k xcb-util-cursor x86_64 0.1.4-3.fc39 fedora 19 k xcb-util-image x86_64 0.4.1-3.fc39 fedora 19 k xcb-util-keysyms x86_64 0.4.1-3.fc39 fedora 14 k xcb-util-renderutil x86_64 0.3.10-3.fc39 fedora 17 k xcb-util-wm x86_64 0.4.2-3.fc39 fedora 31 k xkeyboard-config noarch 2.40-1.fc39 updates 971 k xml-common noarch 0.6.3-61.fc39 fedora 31 k xprop x86_64 1.2.5-4.fc39 fedora 35 k xvidcore x86_64 1.3.7-10.fc39 fedora 267 k zeromq x86_64 4.3.4-8.fc39 fedora 462 k zimg x86_64 3.0.5-1.fc39 updates 291 k zvbi x86_64 0.2.42-1.fc39 updates 433 k Transaction Summary ================================================================================ Install 249 Packages Total download size: 145 M Installed size: 522 M Downloading Packages: (1/249): abattis-cantarell-vf-fonts-0.301-10.fc 510 kB/s | 121 kB 00:00 (2/249): avahi-libs-0.8-24.fc39.x86_64.rpm 1.0 MB/s | 67 kB 00:00 (3/249): adwaita-icon-theme-45.0-1.fc39.noarch. 1.3 MB/s | 407 kB 00:00 (4/249): adwaita-cursor-theme-45.0-1.fc39.noarc 1.8 MB/s | 678 kB 00:00 (5/249): cairo-gobject-1.18.0-1.fc39.x86_64.rpm 253 kB/s | 19 kB 00:00 (6/249): cdparanoia-libs-10.2-42.fc39.x86_64.rp 650 kB/s | 54 kB 00:00 (7/249): cairo-1.18.0-1.fc39.x86_64.rpm 4.3 MB/s | 710 kB 00:00 (8/249): codec2-1.2.0-2.fc39.x86_64.rpm 5.6 MB/s | 638 kB 00:00 (9/249): colord-libs-1.4.6-6.fc39.x86_64.rpm 2.9 MB/s | 233 kB 00:00 (10/249): dbus-1.14.10-1.fc39.x86_64.rpm 103 kB/s | 8.1 kB 00:00 (11/249): dbus-common-1.14.10-1.fc39.noarch.rpm 278 kB/s | 15 kB 00:00 (12/249): dbus-libs-1.14.10-1.fc39.x86_64.rpm 2.6 MB/s | 156 kB 00:00 (13/249): default-fonts-core-sans-4.0-9.fc39.no 494 kB/s | 32 kB 00:00 (14/249): desktop-file-utils-0.26-9.fc39.x86_64 1.0 MB/s | 72 kB 00:00 (15/249): double-conversion-3.1.5-9.fc39.x86_64 668 kB/s | 49 kB 00:00 (16/249): duktape-2.7.0-5.fc39.x86_64.rpm 2.0 MB/s | 170 kB 00:00 (17/249): fdk-aac-free-2.0.0-11.fc39.x86_64.rpm 3.8 MB/s | 336 kB 00:00 (18/249): fonts-filesystem-2.0.5-12.fc39.noarch 127 kB/s | 8.2 kB 00:00 (19/249): flac-libs-1.4.3-2.fc39.x86_64.rpm 2.8 MB/s | 264 kB 00:00 (20/249): freetype-2.13.1-2.fc39.x86_64.rpm 4.0 MB/s | 414 kB 00:00 (21/249): fribidi-1.0.13-2.fc39.x86_64.rpm 1.2 MB/s | 91 kB 00:00 (22/249): game-music-emu-0.6.3-12.fc39.x86_64.r 2.0 MB/s | 156 kB 00:00 (23/249): gdk-pixbuf2-modules-2.42.10-5.fc39.x8 1.3 MB/s | 85 kB 00:00 (24/249): gdk-pixbuf2-2.42.10-5.fc39.x86_64.rpm 4.6 MB/s | 484 kB 00:00 (25/249): glx-utils-9.0.0-3.fc39.x86_64.rpm 1.1 MB/s | 77 kB 00:00 (26/249): graphene-1.10.6-6.fc39.x86_64.rpm 1.1 MB/s | 61 kB 00:00 (27/249): gupnp-igd-1.6.0-2.fc39.x86_64.rpm 603 kB/s | 34 kB 00:00 (28/249): graphite2-1.3.14-12.fc39.x86_64.rpm 896 kB/s | 95 kB 00:00 (29/249): gsm-1.0.22-3.fc39.x86_64.rpm 297 kB/s | 35 kB 00:00 (30/249): harfbuzz-8.2.1-2.fc39.x86_64.rpm 10 MB/s | 975 kB 00:00 (31/249): hicolor-icon-theme-0.17-16.fc39.noarc 780 kB/s | 66 kB 00:00 (32/249): ilbc-3.0.4-7.fc39.x86_64.rpm 478 kB/s | 53 kB 00:00 (33/249): jbigkit-libs-2.1-26.fc39.x86_64.rpm 675 kB/s | 53 kB 00:00 (34/249): iso-codes-4.15.0-2.fc39.noarch.rpm 26 MB/s | 3.5 MB 00:00 (35/249): json-glib-1.8.0-1.fc39.x86_64.rpm 1.6 MB/s | 166 kB 00:00 (36/249): kmod-libs-30-6.fc39.x86_64.rpm 664 kB/s | 67 kB 00:00 (37/249): lame-libs-3.100-15.fc39.x86_64.rpm 5.8 MB/s | 337 kB 00:00 (38/249): lcms2-2.15-2.fc39.x86_64.rpm 2.1 MB/s | 177 kB 00:00 (39/249): libSM-1.2.3-13.fc39.x86_64.rpm 519 kB/s | 41 kB 00:00 (40/249): libICE-1.0.10-11.fc39.x86_64.rpm 727 kB/s | 70 kB 00:00 (41/249): libXcomposite-0.4.5-10.fc39.x86_64.rp 467 kB/s | 23 kB 00:00 (42/249): libXau-1.0.11-3.fc39.x86_64.rpm 319 kB/s | 31 kB 00:00 (43/249): libXcursor-1.2.1-4.fc39.x86_64.rpm 288 kB/s | 30 kB 00:00 (44/249): libXdamage-1.1.5-10.fc39.x86_64.rpm 359 kB/s | 22 kB 00:00 (45/249): libXext-1.3.5-3.fc39.x86_64.rpm 497 kB/s | 39 kB 00:00 (46/249): libXft-2.3.8-3.fc39.x86_64.rpm 1.0 MB/s | 72 kB 00:00 (47/249): libXfixes-6.0.0-6.fc39.x86_64.rpm 177 kB/s | 19 kB 00:00 (48/249): libXi-1.8.1-2.fc39.x86_64.rpm 441 kB/s | 40 kB 00:00 (49/249): libXinerama-1.1.5-3.fc39.x86_64.rpm 314 kB/s | 14 kB 00:00 (50/249): libXrender-0.9.11-3.fc39.x86_64.rpm 338 kB/s | 27 kB 00:00 (51/249): libXv-1.0.11-19.fc39.x86_64.rpm 246 kB/s | 18 kB 00:00 (52/249): libXtst-1.2.4-3.fc39.x86_64.rpm 231 kB/s | 20 kB 00:00 (53/249): libasyncns-0.8-25.fc39.x86_64.rpm 550 kB/s | 30 kB 00:00 (54/249): libXxf86vm-1.1.5-3.fc39.x86_64.rpm 181 kB/s | 18 kB 00:00 (55/249): libb2-0.98.1-9.fc39.x86_64.rpm 289 kB/s | 25 kB 00:00 (56/249): libbluray-1.3.4-3.fc39.x86_64.rpm 3.0 MB/s | 172 kB 00:00 (57/249): libchromaprint-1.5.1-13.fc39.x86_64.r 887 kB/s | 40 kB 00:00 (58/249): libdatrie-0.2.13-7.fc39.x86_64.rpm 628 kB/s | 32 kB 00:00 (59/249): libdav1d-1.2.1-2.fc39.x86_64.rpm 12 MB/s | 618 kB 00:00 (60/249): libepoxy-1.5.10-4.fc39.x86_64.rpm 2.7 MB/s | 234 kB 00:00 (61/249): libgcrypt-1.10.2-2.fc39.x86_64.rpm 7.2 MB/s | 507 kB 00:00 (62/249): libevdev-1.13.1-2.fc39.x86_64.rpm 548 kB/s | 44 kB 00:00 (63/249): libglvnd-egl-1.7.0-1.fc39.x86_64.rpm 724 kB/s | 36 kB 00:00 (64/249): libglvnd-1.7.0-1.fc39.x86_64.rpm 2.2 MB/s | 133 kB 00:00 (65/249): libglvnd-glx-1.7.0-1.fc39.x86_64.rpm 2.2 MB/s | 142 kB 00:00 (66/249): libglvnd-opengl-1.7.0-1.fc39.x86_64.r 1.3 MB/s | 42 kB 00:00 (67/249): libgudev-238-2.fc39.x86_64.rpm 757 kB/s | 35 kB 00:00 (68/249): libgpg-error-1.47-2.fc39.x86_64.rpm 3.9 MB/s | 230 kB 00:00 (69/249): libjpeg-turbo-2.1.4-3.fc39.x86_64.rpm 3.4 MB/s | 183 kB 00:00 (70/249): libmodplug-0.8.9.0-17.fc39.x86_64.rpm 3.6 MB/s | 176 kB 00:00 (71/249): liblerc-4.0.0-4.fc39.x86_64.rpm 1.8 MB/s | 201 kB 00:00 (72/249): libnice-0.1.21-4.fc39.x86_64.rpm 3.6 MB/s | 200 kB 00:00 (73/249): libogg-1.3.5-6.fc39.x86_64.rpm 420 kB/s | 33 kB 00:00 (74/249): libpciaccess-0.16-9.fc39.x86_64.rpm 355 kB/s | 26 kB 00:00 (75/249): librabbitmq-0.13.0-3.fc39.x86_64.rpm 790 kB/s | 43 kB 00:00 (76/249): libpng-1.6.37-15.fc39.x86_64.rpm 1.0 MB/s | 119 kB 00:00 (77/249): librist-0.2.7-2.fc39.x86_64.rpm 1.2 MB/s | 77 kB 00:00 (78/249): libicu-73.2-2.fc39.x86_64.rpm 25 MB/s | 11 MB 00:00 (79/249): libsndfile-1.1.0-9.fc39.x86_64.rpm 2.4 MB/s | 215 kB 00:00 (80/249): libstemmer-2.2.0-7.fc39.x86_64.rpm 1.9 MB/s | 171 kB 00:00 (81/249): libtalloc-2.4.1-1.fc39.x86_64.rpm 572 kB/s | 30 kB 00:00 (82/249): libtdb-1.4.9-1.fc39.x86_64.rpm 861 kB/s | 51 kB 00:00 (83/249): libtevent-0.15.0-1.fc39.x86_64.rpm 1.3 MB/s | 45 kB 00:00 (84/249): libtiff-4.4.0-8.fc39.x86_64.rpm 3.1 MB/s | 202 kB 00:00 (85/249): libthai-0.1.29-6.fc39.x86_64.rpm 2.0 MB/s | 213 kB 00:00 (86/249): libtheora-1.1.1-34.fc39.x86_64.rpm 1.5 MB/s | 166 kB 00:00 (87/249): libtracker-sparql-3.6.0-1.fc39.x86_64 5.6 MB/s | 374 kB 00:00 (88/249): libvdpau-1.5-4.fc39.x86_64.rpm 338 kB/s | 16 kB 00:00 (89/249): libudfread-1.1.2-6.fc39.x86_64.rpm 335 kB/s | 35 kB 00:00 (90/249): libunwind-1.7.0-0.2.rc2.fc39.x86_64.r 682 kB/s | 70 kB 00:00 (91/249): libvmaf-2.3.0-6.fc39.x86_64.rpm 2.8 MB/s | 180 kB 00:00 (92/249): libvisual-0.4.1-2.fc39.x86_64.rpm 1.9 MB/s | 151 kB 00:00 (93/249): libvorbis-1.3.7-8.fc39.x86_64.rpm 1.9 MB/s | 195 kB 00:00 (94/249): libwayland-client-1.22.0-2.fc39.x86_6 496 kB/s | 34 kB 00:00 (95/249): libwayland-cursor-1.22.0-2.fc39.x86_6 332 kB/s | 19 kB 00:00 (96/249): libwayland-egl-1.22.0-2.fc39.x86_64.r 274 kB/s | 13 kB 00:00 (97/249): libwayland-server-1.22.0-2.fc39.x86_6 761 kB/s | 42 kB 00:00 (98/249): libxcb-1.13.1-12.fc39.x86_64.rpm 4.5 MB/s | 233 kB 00:00 (99/249): libwebp-1.3.2-2.fc39.x86_64.rpm 3.4 MB/s | 284 kB 00:00 (100/249): libxshmfence-1.3-13.fc39.x86_64.rpm 222 kB/s | 12 kB 00:00 (101/249): mpdecimal-2.5.1-7.fc39.x86_64.rpm 1.1 MB/s | 89 kB 00:00 (102/249): mpg123-libs-1.31.3-2.fc39.x86_64.rpm 3.8 MB/s | 340 kB 00:00 (103/249): mtdev-1.1.6-6.fc39.x86_64.rpm 509 kB/s | 20 kB 00:00 (104/249): nettle-3.9.1-2.fc39.x86_64.rpm 3.8 MB/s | 425 kB 00:00 (105/249): lpcnetfreedv-0.5-3.fc39.x86_64.rpm 29 MB/s | 7.3 MB 00:00 (106/249): ocl-icd-2.3.2-2.fc39.x86_64.rpm 512 kB/s | 67 kB 00:00 (107/249): openpgm-5.2.122-32.fc39.x86_64.rpm 3.3 MB/s | 176 kB 00:00 (108/249): opencore-amr-0.1.6-4.fc39.x86_64.rpm 2.0 MB/s | 177 kB 00:00 (109/249): opus-1.3.1-13.fc39.x86_64.rpm 1.9 MB/s | 205 kB 00:00 (110/249): orc-0.4.33-3.fc39.x86_64.rpm 3.1 MB/s | 202 kB 00:00 (111/249): pango-1.51.0-1.fc39.x86_64.rpm 4.5 MB/s | 343 kB 00:00 (112/249): pixman-0.42.2-2.fc39.x86_64.rpm 4.9 MB/s | 288 kB 00:00 (113/249): pcre2-utf16-10.42-1.fc39.2.x86_64.rp 2.8 MB/s | 212 kB 00:00 (114/249): python3-dbus-1.3.2-4.fc39.x86_64.rpm 4.4 MB/s | 157 kB 00:00 (115/249): pulseaudio-libs-16.1-5.fc39.x86_64.r 7.5 MB/s | 694 kB 00:00 (116/249): python3-rpm-generators-14-7.fc39.noa 539 kB/s | 30 kB 00:00 (117/249): python3-packaging-23.1-4.fc39.noarch 1.1 MB/s | 114 kB 00:00 (118/249): shared-mime-info-2.2-4.fc39.x86_64.r 5.0 MB/s | 380 kB 00:00 (119/249): snappy-1.1.10-2.fc39.x86_64.rpm 816 kB/s | 37 kB 00:00 (120/249): srt-libs-1.5.3-1.fc39.x86_64.rpm 7.1 MB/s | 370 kB 00:00 (121/249): soxr-0.1.3-14.fc39.x86_64.rpm 792 kB/s | 84 kB 00:00 (122/249): speex-1.2.0-15.fc39.x86_64.rpm 665 kB/s | 67 kB 00:00 (123/249): svt-av1-libs-1.4.1-3.fc39.x86_64.rpm 28 MB/s | 2.0 MB 00:00 (124/249): vapoursynth-libs-63-2.fc39.x86_64.rp 11 MB/s | 567 kB 00:00 (125/249): tslib-1.22-9.fc39.x86_64.rpm 1.2 MB/s | 154 kB 00:00 (126/249): twolame-libs-0.4.0-3.fc39.x86_64.rpm 497 kB/s | 69 kB 00:00 (127/249): vo-amrwbenc-0.1.3-19.fc39.x86_64.rpm 1.2 MB/s | 80 kB 00:00 (128/249): xcb-util-image-0.4.1-3.fc39.x86_64.r 396 kB/s | 19 kB 00:00 (129/249): xcb-util-0.4.1-3.fc39.x86_64.rpm 199 kB/s | 18 kB 00:00 (130/249): xcb-util-cursor-0.1.4-3.fc39.x86_64. 291 kB/s | 19 kB 00:00 (131/249): xcb-util-keysyms-0.4.1-3.fc39.x86_64 412 kB/s | 14 kB 00:00 (132/249): xcb-util-renderutil-0.3.10-3.fc39.x8 515 kB/s | 17 kB 00:00 (133/249): xcb-util-wm-0.4.2-3.fc39.x86_64.rpm 727 kB/s | 31 kB 00:00 (134/249): xprop-1.2.5-4.fc39.x86_64.rpm 755 kB/s | 35 kB 00:00 (135/249): xml-common-0.6.3-61.fc39.noarch.rpm 550 kB/s | 31 kB 00:00 (136/249): xvidcore-1.3.7-10.fc39.x86_64.rpm 3.8 MB/s | 267 kB 00:00 (137/249): zeromq-4.3.4-8.fc39.x86_64.rpm 5.6 MB/s | 462 kB 00:00 (138/249): at-spi2-atk-2.50.2-1.fc39.x86_64.rpm 134 kB/s | 86 kB 00:00 (139/249): at-spi2-core-2.50.2-1.fc39.x86_64.rp 704 kB/s | 371 kB 00:00 (140/249): atk-2.50.2-1.fc39.x86_64.rpm 454 kB/s | 81 kB 00:00 (141/249): bluez-libs-5.77-1.fc39.x86_64.rpm 435 kB/s | 85 kB 00:00 (142/249): cjson-1.7.17-1.fc39.x86_64.rpm 280 kB/s | 32 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://ftp-osl.osuosl.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2605:bc80:3010::134) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://ftp-osl.osuosl.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2605:bc80:3010::134) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://ohioix.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 134.195.207.11) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://ohioix.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 134.195.207.11) (143/249): alsa-lib-1.2.12-1.fc39.x86_64.rpm 200 kB/s | 521 kB 00:02 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://cofractal-sea.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2606:7940:32:22::10) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://cofractal-sea.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2606:7940:32:22::10) (144/249): dbus-broker-36-2.fc39.x86_64.rpm 505 kB/s | 176 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://mirror.servaxnet.com/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2602:ff1a:501:1000::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirror.servaxnet.com/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2602:ff1a:501:1000::2) (145/249): emacs-filesystem-29.4-2.fc39.noarch. 86 kB/s | 7.3 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://ix-denver.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2607:dc0::11) (146/249): expat-2.6.3-1.fc39.x86_64.rpm 671 kB/s | 114 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://ix-denver.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2607:dc0::11) (147/249): SDL2-2.28.5-1.fc39.x86_64.rpm 210 kB/s | 692 kB 00:03 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://ftp-chi.osuosl.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2600:3402:200:227::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://ftp-chi.osuosl.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2600:3402:200:227::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://cofractal-ewr.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2606:7940:52:10::10) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://cofractal-ewr.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2606:7940:52:10::10) (148/249): fontconfig-2.14.2-6.fc39.x86_64.rpm 698 kB/s | 296 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://codingflyboy.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2602:809:b000::16) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://codingflyboy.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2602:809:b000::16) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://forksystems.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:39:6000:103::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://forksystems.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:39:6000:103::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://opencolo.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2607:f358:1a:15::50) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://opencolo.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2607:f358:1a:15::50) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirror.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:13b:0:1000::16) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://mirror.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:13b:0:1000::16) (149/249): gnutls-3.8.6-1.fc39.x86_64.rpm 796 kB/s | 1.1 MB 00:01 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirror.metrocast.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 65.175.128.102) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://mirror.us.mirhosting.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2a03:afc0:3:1508::) (150/249): google-noto-fonts-common-20240101-1. 196 kB/s | 17 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirror.us.mirhosting.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2a03:afc0:3:1508::) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirror.tornadovps.com/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2605:2700:0:2:216:3eff:fed1:f9cb) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://mirrors.rit.edu/fedora/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:8d:8000:15:1ead:ed:c0:ffe) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirrors.rit.edu/fedora/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:8d:8000:15:1ead:ed:c0:ffe) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://ftp-nyc.osuosl.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2600:3404:200:237::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://ftp-nyc.osuosl.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2600:3404:200:237::2) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://download-ib01.fedoraproject.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2600:2701:4000:5211:dead:beef:fe:fed6) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://download-ib01.fedoraproject.org/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2600:2701:4000:5211:dead:beef:fe:fed6) (151/249): google-noto-sans-vf-fonts-20240101-1 765 kB/s | 593 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://nullroute.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:138:5000:1006::194) (152/249): gssdp-1.6.3-1.fc39.x86_64.rpm 323 kB/s | 58 kB 00:00 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://nullroute.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2620:138:5000:1006::194) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirrors.lug.mtu.edu/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 141.219.188.21) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://mirrors.lug.mtu.edu/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 141.219.188.21) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://mirror.math.princeton.edu/pub/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 128.112.18.21) (153/249): glib2-2.78.6-1.fc39.x86_64.rpm 893 kB/s | 2.8 MB 00:03 [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://volico.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 208.68.237.5) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://volico.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 208.68.237.5) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for https://nnenix.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2610:48:200:974::47) [MIRROR] cups-libs-2.4.10-7.fc39.x86_64.rpm: Status code: 404 for http://nnenix.mm.fcix.net/fedora/linux/updates/39/Everything/x86_64/Packages/c/cups-libs-2.4.10-7.fc39.x86_64.rpm (IP: 2610:48:200:974::47) (154/249): gstreamer1-plugins-bad-free-libs-1.2 2.1 MB/s | 767 kB 00:00 (155/249): cups-libs-2.4.10-7.fc39.x86_64.rpm 52 kB/s | 268 kB 00:05 (156/249): gstreamer1-1.22.12-1.fc39.x86_64.rpm 1.5 MB/s | 1.4 MB 00:00 (157/249): gtk-update-icon-cache-3.24.43-1.fc39 79 kB/s | 34 kB 00:00 (158/249): gupnp-1.6.6-1.fc39.x86_64.rpm 631 kB/s | 107 kB 00:00 (159/249): gstreamer1-plugins-base-1.22.12-1.fc 2.9 MB/s | 2.2 MB 00:00 (160/249): highway-1.1.0-1.fc39.x86_64.rpm 1.8 MB/s | 496 kB 00:00 (161/249): libX11-1.8.9-1.fc39.x86_64.rpm 3.7 MB/s | 650 kB 00:00 (162/249): hwdata-0.388-1.fc39.noarch.rpm 4.7 MB/s | 1.6 MB 00:00 (163/249): libX11-common-1.8.9-1.fc39.noarch.rp 1.9 MB/s | 176 kB 00:00 (164/249): libX11-xcb-1.8.9-1.fc39.x86_64.rpm 137 kB/s | 12 kB 00:00 (165/249): libXrandr-1.5.4-1.fc39.x86_64.rpm 315 kB/s | 27 kB 00:00 (166/249): gtk3-3.24.43-1.fc39.x86_64.rpm 4.6 MB/s | 5.6 MB 00:01 (167/249): libaom-3.9.0-1.fc39.x86_64.rpm 5.1 MB/s | 1.8 MB 00:00 (168/249): libavcodec-free-6.1.2-1.fc39.x86_64. 12 MB/s | 4.1 MB 00:00 (169/249): libavformat-free-6.1.2-1.fc39.x86_64 6.0 MB/s | 1.1 MB 00:00 (170/249): libavutil-free-6.1.2-1.fc39.x86_64.r 3.9 MB/s | 354 kB 00:00 (171/249): libcloudproviders-0.3.5-1.fc39.x86_6 517 kB/s | 46 kB 00:00 (172/249): libdecor-0.2.2-1.fc39.x86_64.rpm 544 kB/s | 59 kB 00:00 (173/249): libdrm-2.4.121-1.fc39.x86_64.rpm 1.4 MB/s | 157 kB 00:00 (174/249): libgusb-0.4.9-1.fc39.x86_64.rpm 566 kB/s | 65 kB 00:00 (175/249): libinput-1.25.0-5.fc39.x86_64.rpm 1.7 MB/s | 215 kB 00:00 (176/249): libldb-2.8.1-1.fc39.x86_64.rpm 1.6 MB/s | 181 kB 00:00 (177/249): libproxy-0.5.5-1.fc39.x86_64.rpm 458 kB/s | 48 kB 00:00 (178/249): libopenmpt-0.7.8-1.fc39.x86_64.rpm 3.7 MB/s | 686 kB 00:00 (179/249): libjxl-0.8.3-1.fc39.x86_64.rpm 3.6 MB/s | 1.2 MB 00:00 (180/249): libseccomp-2.5.5-1.fc39.x86_64.rpm 648 kB/s | 70 kB 00:00 (181/249): librsvg2-2.57.1-2.fc39.x86_64.rpm 14 MB/s | 1.6 MB 00:00 (182/249): libsmbclient-4.19.8-1.fc39.x86_64.rp 738 kB/s | 76 kB 00:00 (183/249): libsodium-1.0.18-15.fc39.x86_64.rpm 1.6 MB/s | 162 kB 00:00 (184/249): libswresample-free-6.1.2-1.fc39.x86_ 701 kB/s | 67 kB 00:00 (185/249): libsoup3-3.4.4-1.fc39.x86_64.rpm 3.0 MB/s | 389 kB 00:00 (186/249): libswscale-free-6.1.2-1.fc39.x86_64. 1.7 MB/s | 188 kB 00:00 (187/249): libusb1-1.0.27-2.fc39.x86_64.rpm 789 kB/s | 76 kB 00:00 (188/249): libvpl-2.13.0-1.fc39.x86_64.rpm 1.6 MB/s | 154 kB 00:00 (189/249): libwacom-2.10.0-1.fc39.x86_64.rpm 494 kB/s | 43 kB 00:00 (190/249): libwacom-data-2.10.0-1.fc39.noarch.r 2.1 MB/s | 196 kB 00:00 (191/249): libva-2.20.0-2.fc39.x86_64.rpm 305 kB/s | 107 kB 00:00 (192/249): libwbclient-4.19.8-1.fc39.x86_64.rpm 527 kB/s | 45 kB 00:00 (193/249): libxkbcommon-1.6.0-1.fc39.x86_64.rpm 1.6 MB/s | 142 kB 00:00 (194/249): libvpx-1.13.1-1.fc39.x86_64.rpm 3.1 MB/s | 1.1 MB 00:00 (195/249): libxkbcommon-x11-1.6.0-1.fc39.x86_64 251 kB/s | 22 kB 00:00 (196/249): lmdb-libs-0.9.33-1.fc39.x86_64.rpm 703 kB/s | 61 kB 00:00 (197/249): mesa-filesystem-23.3.6-1.fc39.x86_64 214 kB/s | 19 kB 00:00 (198/249): mesa-libEGL-23.3.6-1.fc39.x86_64.rpm 1.5 MB/s | 134 kB 00:00 (199/249): mbedtls-2.28.8-1.fc39.x86_64.rpm 2.2 MB/s | 403 kB 00:00 (200/249): mesa-libgbm-23.3.6-1.fc39.x86_64.rpm 539 kB/s | 46 kB 00:00 (201/249): mesa-libglapi-23.3.6-1.fc39.x86_64.r 619 kB/s | 53 kB 00:00 (202/249): mesa-libGL-23.3.6-1.fc39.x86_64.rpm 1.7 MB/s | 176 kB 00:00 (203/249): pyproject-rpm-macros-1.15.1-1.fc39.n 452 kB/s | 43 kB 00:00 (204/249): openjpeg2-2.5.2-1.fc39.x86_64.rpm 1.7 MB/s | 178 kB 00:00 (205/249): python-pip-wheel-23.2.1-2.fc39.noarc 8.1 MB/s | 1.5 MB 00:00 (206/249): python-rpm-macros-3.12-8.fc39.noarch 193 kB/s | 18 kB 00:00 (207/249): python-pyqt6-rpm-macros-6.6.1-5.fc39 99 kB/s | 9.4 kB 00:00 (208/249): python3-3.12.7-1.fc39.x86_64.rpm 326 kB/s | 28 kB 00:00 (209/249): python3-devel-3.12.7-1.fc39.x86_64.r 3.1 MB/s | 314 kB 00:00 (210/249): python3-pyqt6-6.6.1-5.fc39.x86_64.rp 5.0 MB/s | 1.1 MB 00:00 (211/249): python3-pyqt6-base-6.6.1-5.fc39.x86_ 13 MB/s | 3.3 MB 00:00 (212/249): python3-pyqt6-sip-13.6.0-1.fc39.x86_ 697 kB/s | 77 kB 00:00 (213/249): python3-rpm-macros-3.12-8.fc39.noarc 132 kB/s | 12 kB 00:00 (214/249): python3-setuptools-67.7.2-8.fc39.noa 7.8 MB/s | 1.5 MB 00:00 (215/249): qt6-qtbase-common-6.6.2-2.fc39.noarc 119 kB/s | 11 kB 00:00 (216/249): qt6-qtbase-6.6.2-2.fc39.x86_64.rpm 13 MB/s | 3.9 MB 00:00 (217/249): qt6-qtconnectivity-6.6.2-1.fc39.x86_ 4.7 MB/s | 470 kB 00:00 (218/249): qt6-qtdeclarative-6.6.2-3.fc39.x86_6 20 MB/s | 9.6 MB 00:00 (219/249): qt6-qtbase-gui-6.6.2-2.fc39.x86_64.r 12 MB/s | 7.3 MB 00:00 (220/249): qt6-qtmultimedia-6.6.2-1.fc39.x86_64 9.1 MB/s | 1.0 MB 00:00 (221/249): qt6-qtpositioning-6.6.2-1.fc39.x86_6 4.3 MB/s | 443 kB 00:00 (222/249): qt6-qtpdf-6.6.2-1.fc39.x86_64.rpm 12 MB/s | 2.4 MB 00:00 (223/249): qt6-qtquicktimeline-6.6.2-1.fc39.x86 541 kB/s | 59 kB 00:00 (224/249): qt6-qtremoteobjects-6.6.2-1.fc39.x86 4.3 MB/s | 475 kB 00:00 (225/249): qt6-qtquick3d-6.6.2-1.fc39.x86_64.rp 14 MB/s | 4.1 MB 00:00 (226/249): qt6-qtsensors-6.6.2-1.fc39.x86_64.rp 2.1 MB/s | 226 kB 00:00 (227/249): qt6-qtserialport-6.6.2-1.fc39.x86_64 808 kB/s | 76 kB 00:00 (228/249): python3-libs-3.12.7-1.fc39.x86_64.rp 4.7 MB/s | 9.2 MB 00:01 (229/249): qt6-qtshadertools-6.6.2-1.fc39.x86_6 13 MB/s | 1.4 MB 00:00 (230/249): qt6-qtspeech-6.6.2-1.fc39.x86_64.rpm 1.1 MB/s | 111 kB 00:00 (231/249): qt6-qttools-common-6.6.2-1.fc39.noar 112 kB/s | 11 kB 00:00 (232/249): qt6-qtsvg-6.6.2-1.fc39.x86_64.rpm 984 kB/s | 206 kB 00:00 (233/249): qt6-qttools-libs-help-6.6.2-1.fc39.x 2.0 MB/s | 199 kB 00:00 (234/249): qt6-qttools-libs-designer-6.6.2-1.fc 14 MB/s | 2.9 MB 00:00 (235/249): qt6-qtwebchannel-6.6.2-1.fc39.x86_64 1.3 MB/s | 151 kB 00:00 (236/249): qt6-qtwebsockets-6.6.2-1.fc39.x86_64 811 kB/s | 104 kB 00:00 (237/249): rav1e-libs-0.7.1-4.fc39.x86_64.rpm 8.7 MB/s | 1.0 MB 00:00 (238/249): rsvg-pixbuf-loader-2.57.1-2.fc39.x86 133 kB/s | 16 kB 00:00 (239/249): samba-common-4.19.8-1.fc39.noarch.rp 1.2 MB/s | 150 kB 00:00 (240/249): samba-common-libs-4.19.8-1.fc39.x86_ 826 kB/s | 107 kB 00:00 (241/249): samba-client-libs-4.19.8-1.fc39.x86_ 15 MB/s | 5.2 MB 00:00 (242/249): systemd-pam-254.18-1.fc39.x86_64.rpm 1.7 MB/s | 357 kB 00:00 (243/249): systemd-rpm-macros-254.18-1.fc39.noa 298 kB/s | 25 kB 00:00 (244/249): systemd-254.18-1.fc39.x86_64.rpm 15 MB/s | 4.7 MB 00:00 (245/249): vulkan-loader-1.3.275.0-1.fc39.x86_6 1.7 MB/s | 149 kB 00:00 (246/249): xkeyboard-config-2.40-1.fc39.noarch. 9.6 MB/s | 971 kB 00:00 (247/249): zimg-3.0.5-1.fc39.x86_64.rpm 2.9 MB/s | 291 kB 00:00 (248/249): tzdata-2024a-2.fc39.noarch.rpm 2.7 MB/s | 715 kB 00:00 (249/249): zvbi-0.2.42-1.fc39.x86_64.rpm 4.6 MB/s | 433 kB 00:00 -------------------------------------------------------------------------------- Total 8.6 MB/s | 145 MB 00:16 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : libpng-2:1.6.37-15.fc39.x86_64 1/249 Installing : dbus-libs-1:1.14.10-1.fc39.x86_64 2/249 Installing : libwayland-client-1.22.0-2.fc39.x86_64 3/249 Installing : libogg-2:1.3.5-6.fc39.x86_64 4/249 Installing : libX11-xcb-1.8.9-1.fc39.x86_64 5/249 Installing : expat-2.6.3-1.fc39.x86_64 6/249 Installing : libtalloc-2.4.1-1.fc39.x86_64 7/249 Installing : libvorbis-1:1.3.7-8.fc39.x86_64 8/249 Installing : libjpeg-turbo-2.1.4-3.fc39.x86_64 9/249 Installing : libicu-73.2-2.fc39.x86_64 10/249 Installing : libtevent-0.15.0-1.fc39.x86_64 11/249 Installing : libwayland-cursor-1.22.0-2.fc39.x86_64 12/249 Installing : python-rpm-macros-3.12-8.fc39.noarch 13/249 Installing : opus-1.3.1-13.fc39.x86_64 14/249 Installing : libtdb-1.4.9-1.fc39.x86_64 15/249 Installing : libglvnd-1:1.7.0-1.fc39.x86_64 16/249 Installing : fonts-filesystem-1:2.0.5-12.fc39.noarch 17/249 Installing : libglvnd-opengl-1:1.7.0-1.fc39.x86_64 18/249 Installing : python3-rpm-macros-3.12-8.fc39.noarch 19/249 Installing : libtheora-1:1.1.1-34.fc39.x86_64 20/249 Installing : avahi-libs-0.8-24.fc39.x86_64 21/249 Installing : qt6-qttools-common-6.6.2-1.fc39.noarch 22/249 Installing : mesa-libglapi-23.3.6-1.fc39.x86_64 23/249 Installing : libvpl-1:2.13.0-1.fc39.x86_64 24/249 Running scriptlet: xml-common-0.6.3-61.fc39.noarch 25/249 Installing : xml-common-0.6.3-61.fc39.noarch 25/249 Installing : nettle-3.9.1-2.fc39.x86_64 26/249 Installing : gnutls-3.8.6-1.fc39.x86_64 27/249 Installing : glib2-2.78.6-1.fc39.x86_64 28/249 Installing : libsoup3-3.4.4-1.fc39.x86_64 29/249 Installing : gssdp-1.6.3-1.fc39.x86_64 30/249 Installing : json-glib-1.8.0-1.fc39.x86_64 31/249 Installing : libgudev-238-2.fc39.x86_64 32/249 Installing : shared-mime-info-2.2-4.fc39.x86_64 33/249 Running scriptlet: shared-mime-info-2.2-4.fc39.x86_64 33/249 Installing : gdk-pixbuf2-2.42.10-5.fc39.x86_64 34/249 Installing : cups-libs-1:2.4.10-7.fc39.x86_64 35/249 Installing : mtdev-1.1.6-6.fc39.x86_64 36/249 Installing : mpg123-libs-1.31.3-2.fc39.x86_64 37/249 Installing : libxshmfence-1.3-13.fc39.x86_64 38/249 Installing : libwebp-1.3.2-2.fc39.x86_64 39/249 Installing : libwayland-server-1.22.0-2.fc39.x86_64 40/249 Installing : libwayland-egl-1.22.0-2.fc39.x86_64 41/249 Installing : libunwind-1.7.0-0.2.rc2.fc39.x86_64 42/249 Installing : libevdev-1.13.1-2.fc39.x86_64 43/249 Installing : libb2-0.98.1-9.fc39.x86_64 44/249 Installing : libICE-1.0.10-11.fc39.x86_64 45/249 Installing : lcms2-2.15-2.fc39.x86_64 46/249 Installing : lame-libs-3.100-15.fc39.x86_64 47/249 Installing : gsm-1.0.22-3.fc39.x86_64 48/249 Installing : fribidi-1.0.13-2.fc39.x86_64 49/249 Installing : libSM-1.2.3-13.fc39.x86_64 50/249 Installing : libopenmpt-0.7.8-1.fc39.x86_64 51/249 Installing : gtk-update-icon-cache-3.24.43-1.fc39.x86_64 52/249 Installing : graphene-1.10.6-6.fc39.x86_64 53/249 Installing : libcloudproviders-0.3.5-1.fc39.x86_64 54/249 Installing : srt-libs-1.5.3-1.fc39.x86_64 55/249 Installing : iso-codes-4.15.0-2.fc39.noarch 56/249 Installing : pyproject-rpm-macros-1.15.1-1.fc39.noarch 57/249 Installing : abattis-cantarell-vf-fonts-0.301-10.fc39.noarch 58/249 Installing : flac-libs-1.4.3-2.fc39.x86_64 59/249 Installing : libsndfile-1.1.0-9.fc39.x86_64 60/249 Installing : zvbi-0.2.42-1.fc39.x86_64 61/249 Running scriptlet: zvbi-0.2.42-1.fc39.x86_64 61/249 Installing : zimg-3.0.5-1.fc39.x86_64 62/249 Installing : xkeyboard-config-2.40-1.fc39.noarch 63/249 Installing : libxkbcommon-1.6.0-1.fc39.x86_64 64/249 Installing : vulkan-loader-1.3.275.0-1.fc39.x86_64 65/249 Installing : tzdata-2024a-2.fc39.noarch 66/249 Installing : rav1e-libs-0.7.1-4.fc39.x86_64 67/249 Installing : python-pyqt6-rpm-macros-6.6.1-5.fc39.noarch 68/249 Installing : python-pip-wheel-23.2.1-2.fc39.noarch 69/249 Installing : openjpeg2-2.5.2-1.fc39.x86_64 70/249 Installing : mesa-filesystem-23.3.6-1.fc39.x86_64 71/249 Installing : mbedtls-2.28.8-1.fc39.x86_64 72/249 Installing : lmdb-libs-0.9.33-1.fc39.x86_64 73/249 Installing : libldb-2.8.1-1.fc39.x86_64 74/249 Installing : libwacom-data-2.10.0-1.fc39.noarch 75/249 Installing : libvpx-1.13.1-1.fc39.x86_64 76/249 Installing : libusb1-1.0.27-2.fc39.x86_64 77/249 Installing : libgusb-0.4.9-1.fc39.x86_64 78/249 Installing : colord-libs-1.4.6-6.fc39.x86_64 79/249 Installing : libsodium-1.0.18-15.fc39.x86_64 80/249 Installing : libseccomp-2.5.5-1.fc39.x86_64 81/249 Installing : libX11-common-1.8.9-1.fc39.noarch 82/249 Installing : hwdata-0.388-1.fc39.noarch 83/249 Installing : libpciaccess-0.16-9.fc39.x86_64 84/249 Installing : libdrm-2.4.121-1.fc39.x86_64 85/249 Installing : highway-1.1.0-1.fc39.x86_64 86/249 Installing : libjxl-1:0.8.3-1.fc39.x86_64 87/249 Installing : google-noto-fonts-common-20240101-1.fc39.noarch 88/249 Installing : google-noto-sans-vf-fonts-20240101-1.fc39.noarch 89/249 Installing : default-fonts-core-sans-4.0-9.fc39.noarch 90/249 Installing : emacs-filesystem-1:29.4-2.fc39.noarch 91/249 Installing : cjson-1.7.17-1.fc39.x86_64 92/249 Running scriptlet: cjson-1.7.17-1.fc39.x86_64 92/249 Installing : librist-0.2.7-2.fc39.x86_64 93/249 Installing : bluez-libs-5.77-1.fc39.x86_64 94/249 Installing : alsa-lib-1.2.12-1.fc39.x86_64 95/249 Installing : xvidcore-1.3.7-10.fc39.x86_64 96/249 Installing : vo-amrwbenc-0.1.3-19.fc39.x86_64 97/249 Installing : twolame-libs-0.4.0-3.fc39.x86_64 98/249 Installing : svt-av1-libs-1.4.1-3.fc39.x86_64 99/249 Installing : speex-1.2.0-15.fc39.x86_64 100/249 Installing : soxr-0.1.3-14.fc39.x86_64 101/249 Installing : snappy-1.1.10-2.fc39.x86_64 102/249 Installing : pixman-0.42.2-2.fc39.x86_64 103/249 Installing : pcre2-utf16-10.42-1.fc39.2.x86_64 104/249 Installing : orc-0.4.33-3.fc39.x86_64 105/249 Installing : openpgm-5.2.122-32.fc39.x86_64 106/249 Installing : zeromq-4.3.4-8.fc39.x86_64 107/249 Installing : opencore-amr-0.1.6-4.fc39.x86_64 108/249 Installing : ocl-icd-2.3.2-2.fc39.x86_64 109/249 Installing : mpdecimal-2.5.1-7.fc39.x86_64 110/249 Installing : python3-3.12.7-1.fc39.x86_64 111/249 Installing : python3-libs-3.12.7-1.fc39.x86_64 112/249 Installing : gstreamer1-1.22.12-1.fc39.x86_64 113/249 Installing : vapoursynth-libs-63-2.fc39.x86_64 114/249 Installing : python3-dbus-1.3.2-4.fc39.x86_64 115/249 Installing : python3-packaging-23.1-4.fc39.noarch 116/249 Installing : python3-rpm-generators-14-7.fc39.noarch 117/249 Installing : libwacom-2.10.0-1.fc39.x86_64 118/249 Installing : libinput-1.25.0-5.fc39.x86_64 119/249 Running scriptlet: libinput-1.25.0-5.fc39.x86_64 119/249 Installing : python3-pyqt6-sip-13.6.0-1.fc39.x86_64 120/249 Installing : lpcnetfreedv-0.5-3.fc39.x86_64 121/249 Installing : codec2-1.2.0-2.fc39.x86_64 122/249 Installing : libvmaf-2.3.0-6.fc39.x86_64 123/249 Installing : libaom-3.9.0-1.fc39.x86_64 124/249 Installing : libvisual-1:0.4.1-2.fc39.x86_64 125/249 Installing : libudfread-1.1.2-6.fc39.x86_64 126/249 Installing : libstemmer-2.2.0-7.fc39.x86_64 127/249 Installing : libtracker-sparql-3.6.0-1.fc39.x86_64 128/249 Installing : librabbitmq-0.13.0-3.fc39.x86_64 129/249 Installing : libmodplug-1:0.8.9.0-17.fc39.x86_64 130/249 Installing : liblerc-4.0.0-4.fc39.x86_64 131/249 Installing : libgpg-error-1.47-2.fc39.x86_64 132/249 Installing : libgcrypt-1.10.2-2.fc39.x86_64 133/249 Installing : libepoxy-1.5.10-4.fc39.x86_64 134/249 Installing : libdav1d-1.2.1-2.fc39.x86_64 135/249 Installing : libdatrie-0.2.13-7.fc39.x86_64 136/249 Installing : libthai-0.1.29-6.fc39.x86_64 137/249 Installing : libasyncns-0.8-25.fc39.x86_64 138/249 Installing : libXau-1.0.11-3.fc39.x86_64 139/249 Installing : libxcb-1.13.1-12.fc39.x86_64 140/249 Installing : libX11-1.8.9-1.fc39.x86_64 141/249 Installing : libXext-1.3.5-3.fc39.x86_64 142/249 Installing : libXfixes-6.0.0-6.fc39.x86_64 143/249 Installing : libXrender-0.9.11-3.fc39.x86_64 144/249 Installing : libXi-1.8.1-2.fc39.x86_64 145/249 Installing : mesa-libgbm-23.3.6-1.fc39.x86_64 146/249 Installing : libXrandr-1.5.4-1.fc39.x86_64 147/249 Installing : xcb-util-renderutil-0.3.10-3.fc39.x86_64 148/249 Installing : libglvnd-egl-1:1.7.0-1.fc39.x86_64 149/249 Installing : mesa-libEGL-23.3.6-1.fc39.x86_64 150/249 Installing : libXtst-1.2.4-3.fc39.x86_64 151/249 Installing : libXcursor-1.2.1-4.fc39.x86_64 152/249 Installing : libXdamage-1.1.5-10.fc39.x86_64 153/249 Installing : libXinerama-1.1.5-3.fc39.x86_64 154/249 Installing : libXv-1.0.11-19.fc39.x86_64 155/249 Installing : libXxf86vm-1.1.5-3.fc39.x86_64 156/249 Installing : libglvnd-glx-1:1.7.0-1.fc39.x86_64 157/249 Installing : mesa-libGL-23.3.6-1.fc39.x86_64 158/249 Installing : libva-2.20.0-2.fc39.x86_64 159/249 Installing : glx-utils-9.0.0-3.fc39.x86_64 160/249 Installing : libvdpau-1.5-4.fc39.x86_64 161/249 Installing : libavutil-free-6.1.2-1.fc39.x86_64 162/249 Installing : libswresample-free-6.1.2-1.fc39.x86_64 163/249 Installing : libswscale-free-6.1.2-1.fc39.x86_64 164/249 Installing : libXcomposite-0.4.5-10.fc39.x86_64 165/249 Installing : xprop-1.2.5-4.fc39.x86_64 166/249 Installing : pulseaudio-libs-16.1-5.fc39.x86_64 167/249 Installing : xcb-util-0.4.1-3.fc39.x86_64 168/249 Installing : xcb-util-image-0.4.1-3.fc39.x86_64 169/249 Installing : xcb-util-cursor-0.1.4-3.fc39.x86_64 170/249 Installing : xcb-util-keysyms-0.4.1-3.fc39.x86_64 171/249 Installing : xcb-util-wm-0.4.2-3.fc39.x86_64 172/249 Installing : libxkbcommon-x11-1.6.0-1.fc39.x86_64 173/249 Installing : kmod-libs-30-6.fc39.x86_64 174/249 Installing : jbigkit-libs-2.1-26.fc39.x86_64 175/249 Installing : libtiff-4.4.0-8.fc39.x86_64 176/249 Installing : ilbc-3.0.4-7.fc39.x86_64 177/249 Installing : hicolor-icon-theme-0.17-16.fc39.noarch 178/249 Installing : graphite2-1.3.14-12.fc39.x86_64 179/249 Installing : cairo-1.18.0-1.fc39.x86_64 180/249 Installing : harfbuzz-8.2.1-2.fc39.x86_64 181/249 Installing : freetype-2.13.1-2.fc39.x86_64 182/249 Installing : fontconfig-2.14.2-6.fc39.x86_64 183/249 Running scriptlet: fontconfig-2.14.2-6.fc39.x86_64 183/249 Installing : cairo-gobject-1.18.0-1.fc39.x86_64 184/249 Installing : libXft-2.3.8-3.fc39.x86_64 185/249 Installing : pango-1.51.0-1.fc39.x86_64 186/249 Installing : librsvg2-2.57.1-2.fc39.x86_64 187/249 Installing : rsvg-pixbuf-loader-2.57.1-2.fc39.x86_64 188/249 Installing : gdk-pixbuf2-modules-2.42.10-5.fc39.x86_64 189/249 Installing : libbluray-1.3.4-3.fc39.x86_64 190/249 Installing : game-music-emu-0.6.3-12.fc39.x86_64 191/249 Installing : fdk-aac-free-2.0.0-11.fc39.x86_64 192/249 Installing : libavcodec-free-6.1.2-1.fc39.x86_64 193/249 Installing : libchromaprint-1.5.1-13.fc39.x86_64 194/249 Installing : duktape-2.7.0-5.fc39.x86_64 195/249 Installing : libproxy-0.5.5-1.fc39.x86_64 196/249 Installing : double-conversion-3.1.5-9.fc39.x86_64 197/249 Installing : qt6-qtbase-common-6.6.2-2.fc39.noarch 198/249 Installing : qt6-qtbase-6.6.2-2.fc39.x86_64 199/249 Installing : qt6-qtserialport-6.6.2-1.fc39.x86_64 200/249 Installing : qt6-qtconnectivity-6.6.2-1.fc39.x86_64 201/249 Installing : qt6-qtwebsockets-6.6.2-1.fc39.x86_64 202/249 Installing : dbus-common-1:1.14.10-1.fc39.noarch 203/249 Running scriptlet: dbus-common-1:1.14.10-1.fc39.noarch 203/249 Running scriptlet: dbus-broker-36-2.fc39.x86_64 204/249 Installing : dbus-broker-36-2.fc39.x86_64 204/249 Running scriptlet: dbus-broker-36-2.fc39.x86_64 204/249 Installing : dbus-1:1.14.10-1.fc39.x86_64 205/249 Installing : at-spi2-core-2.50.2-1.fc39.x86_64 206/249 Installing : atk-2.50.2-1.fc39.x86_64 207/249 Installing : systemd-pam-254.18-1.fc39.x86_64 208/249 Installing : systemd-254.18-1.fc39.x86_64 209/249 Running scriptlet: systemd-254.18-1.fc39.x86_64 209/249 Creating group 'input' with GID 104. Creating group 'kvm' with GID 36. Creating group 'render' with GID 105. Creating group 'sgx' with GID 106. Creating group 'systemd-journal' with GID 190. Creating group 'systemd-oom' with GID 999. Creating user 'systemd-oom' (systemd Userspace OOM Killer) with UID 999 and GID 999. Running scriptlet: samba-common-2:4.19.8-1.fc39.noarch 210/249 Installing : samba-common-2:4.19.8-1.fc39.noarch 210/249 Running scriptlet: samba-common-2:4.19.8-1.fc39.noarch 210/249 Running scriptlet: libwbclient-2:4.19.8-1.fc39.x86_64 211/249 Installing : libwbclient-2:4.19.8-1.fc39.x86_64 211/249 Installing : samba-common-libs-2:4.19.8-1.fc39.x86_64 212/249 Installing : samba-client-libs-2:4.19.8-1.fc39.x86_64 213/249 Installing : libsmbclient-2:4.19.8-1.fc39.x86_64 214/249 Installing : libavformat-free-6.1.2-1.fc39.x86_64 215/249 Installing : at-spi2-atk-2.50.2-1.fc39.x86_64 216/249 Installing : gupnp-1.6.6-1.fc39.x86_64 217/249 Installing : gupnp-igd-1.6.0-2.fc39.x86_64 218/249 Installing : libnice-0.1.21-4.fc39.x86_64 219/249 Installing : cdparanoia-libs-10.2-42.fc39.x86_64 220/249 Installing : gstreamer1-plugins-base-1.22.12-1.fc39.x86_64 221/249 Installing : gstreamer1-plugins-bad-free-libs-1.22.12-1.fc39. 222/249 Installing : adwaita-cursor-theme-45.0-1.fc39.noarch 223/249 Installing : adwaita-icon-theme-45.0-1.fc39.noarch 224/249 Installing : gtk3-3.24.43-1.fc39.x86_64 225/249 Installing : libdecor-0.2.2-1.fc39.x86_64 226/249 Installing : SDL2-2.28.5-1.fc39.x86_64 227/249 Installing : tslib-1.22-9.fc39.x86_64 228/249 Installing : qt6-qtbase-gui-6.6.2-2.fc39.x86_64 229/249 Installing : qt6-qtdeclarative-6.6.2-3.fc39.x86_64 230/249 Installing : qt6-qtmultimedia-6.6.2-1.fc39.x86_64 231/249 Installing : qt6-qtspeech-6.6.2-1.fc39.x86_64 232/249 Installing : python3-pyqt6-base-6.6.1-5.fc39.x86_64 233/249 Installing : qt6-qtpdf-6.6.2-1.fc39.x86_64 234/249 Installing : qt6-qtpositioning-6.6.2-1.fc39.x86_64 235/249 Installing : qt6-qtquicktimeline-6.6.2-1.fc39.x86_64 236/249 Installing : qt6-qtremoteobjects-6.6.2-1.fc39.x86_64 237/249 Installing : qt6-qtsensors-6.6.2-1.fc39.x86_64 238/249 Installing : qt6-qttools-libs-designer-6.6.2-1.fc39.x86_64 239/249 Installing : qt6-qtwebchannel-6.6.2-1.fc39.x86_64 240/249 Installing : qt6-qtshadertools-6.6.2-1.fc39.x86_64 241/249 Installing : qt6-qtquick3d-6.6.2-1.fc39.x86_64 242/249 Installing : qt6-qtsvg-6.6.2-1.fc39.x86_64 243/249 Installing : qt6-qttools-libs-help-6.6.2-1.fc39.x86_64 244/249 Installing : python3-pyqt6-6.6.1-5.fc39.x86_64 245/249 Installing : python3-devel-3.12.7-1.fc39.x86_64 246/249 Installing : python3-setuptools-67.7.2-8.fc39.noarch 247/249 Installing : desktop-file-utils-0.26-9.fc39.x86_64 248/249 Installing : systemd-rpm-macros-254.18-1.fc39.noarch 249/249 Running scriptlet: fontconfig-2.14.2-6.fc39.x86_64 249/249 Running scriptlet: systemd-rpm-macros-254.18-1.fc39.noarch 249/249 Verifying : abattis-cantarell-vf-fonts-0.301-10.fc39.noarch 1/249 Verifying : adwaita-cursor-theme-45.0-1.fc39.noarch 2/249 Verifying : adwaita-icon-theme-45.0-1.fc39.noarch 3/249 Verifying : avahi-libs-0.8-24.fc39.x86_64 4/249 Verifying : cairo-1.18.0-1.fc39.x86_64 5/249 Verifying : cairo-gobject-1.18.0-1.fc39.x86_64 6/249 Verifying : cdparanoia-libs-10.2-42.fc39.x86_64 7/249 Verifying : codec2-1.2.0-2.fc39.x86_64 8/249 Verifying : colord-libs-1.4.6-6.fc39.x86_64 9/249 Verifying : dbus-1:1.14.10-1.fc39.x86_64 10/249 Verifying : dbus-common-1:1.14.10-1.fc39.noarch 11/249 Verifying : dbus-libs-1:1.14.10-1.fc39.x86_64 12/249 Verifying : default-fonts-core-sans-4.0-9.fc39.noarch 13/249 Verifying : desktop-file-utils-0.26-9.fc39.x86_64 14/249 Verifying : double-conversion-3.1.5-9.fc39.x86_64 15/249 Verifying : duktape-2.7.0-5.fc39.x86_64 16/249 Verifying : fdk-aac-free-2.0.0-11.fc39.x86_64 17/249 Verifying : flac-libs-1.4.3-2.fc39.x86_64 18/249 Verifying : fonts-filesystem-1:2.0.5-12.fc39.noarch 19/249 Verifying : freetype-2.13.1-2.fc39.x86_64 20/249 Verifying : fribidi-1.0.13-2.fc39.x86_64 21/249 Verifying : game-music-emu-0.6.3-12.fc39.x86_64 22/249 Verifying : gdk-pixbuf2-2.42.10-5.fc39.x86_64 23/249 Verifying : gdk-pixbuf2-modules-2.42.10-5.fc39.x86_64 24/249 Verifying : glx-utils-9.0.0-3.fc39.x86_64 25/249 Verifying : graphene-1.10.6-6.fc39.x86_64 26/249 Verifying : graphite2-1.3.14-12.fc39.x86_64 27/249 Verifying : gsm-1.0.22-3.fc39.x86_64 28/249 Verifying : gupnp-igd-1.6.0-2.fc39.x86_64 29/249 Verifying : harfbuzz-8.2.1-2.fc39.x86_64 30/249 Verifying : hicolor-icon-theme-0.17-16.fc39.noarch 31/249 Verifying : ilbc-3.0.4-7.fc39.x86_64 32/249 Verifying : iso-codes-4.15.0-2.fc39.noarch 33/249 Verifying : jbigkit-libs-2.1-26.fc39.x86_64 34/249 Verifying : json-glib-1.8.0-1.fc39.x86_64 35/249 Verifying : kmod-libs-30-6.fc39.x86_64 36/249 Verifying : lame-libs-3.100-15.fc39.x86_64 37/249 Verifying : lcms2-2.15-2.fc39.x86_64 38/249 Verifying : libICE-1.0.10-11.fc39.x86_64 39/249 Verifying : libSM-1.2.3-13.fc39.x86_64 40/249 Verifying : libXau-1.0.11-3.fc39.x86_64 41/249 Verifying : libXcomposite-0.4.5-10.fc39.x86_64 42/249 Verifying : libXcursor-1.2.1-4.fc39.x86_64 43/249 Verifying : libXdamage-1.1.5-10.fc39.x86_64 44/249 Verifying : libXext-1.3.5-3.fc39.x86_64 45/249 Verifying : libXfixes-6.0.0-6.fc39.x86_64 46/249 Verifying : libXft-2.3.8-3.fc39.x86_64 47/249 Verifying : libXi-1.8.1-2.fc39.x86_64 48/249 Verifying : libXinerama-1.1.5-3.fc39.x86_64 49/249 Verifying : libXrender-0.9.11-3.fc39.x86_64 50/249 Verifying : libXtst-1.2.4-3.fc39.x86_64 51/249 Verifying : libXv-1.0.11-19.fc39.x86_64 52/249 Verifying : libXxf86vm-1.1.5-3.fc39.x86_64 53/249 Verifying : libasyncns-0.8-25.fc39.x86_64 54/249 Verifying : libb2-0.98.1-9.fc39.x86_64 55/249 Verifying : libbluray-1.3.4-3.fc39.x86_64 56/249 Verifying : libchromaprint-1.5.1-13.fc39.x86_64 57/249 Verifying : libdatrie-0.2.13-7.fc39.x86_64 58/249 Verifying : libdav1d-1.2.1-2.fc39.x86_64 59/249 Verifying : libepoxy-1.5.10-4.fc39.x86_64 60/249 Verifying : libevdev-1.13.1-2.fc39.x86_64 61/249 Verifying : libgcrypt-1.10.2-2.fc39.x86_64 62/249 Verifying : libglvnd-1:1.7.0-1.fc39.x86_64 63/249 Verifying : libglvnd-egl-1:1.7.0-1.fc39.x86_64 64/249 Verifying : libglvnd-glx-1:1.7.0-1.fc39.x86_64 65/249 Verifying : libglvnd-opengl-1:1.7.0-1.fc39.x86_64 66/249 Verifying : libgpg-error-1.47-2.fc39.x86_64 67/249 Verifying : libgudev-238-2.fc39.x86_64 68/249 Verifying : libicu-73.2-2.fc39.x86_64 69/249 Verifying : libjpeg-turbo-2.1.4-3.fc39.x86_64 70/249 Verifying : liblerc-4.0.0-4.fc39.x86_64 71/249 Verifying : libmodplug-1:0.8.9.0-17.fc39.x86_64 72/249 Verifying : libnice-0.1.21-4.fc39.x86_64 73/249 Verifying : libogg-2:1.3.5-6.fc39.x86_64 74/249 Verifying : libpciaccess-0.16-9.fc39.x86_64 75/249 Verifying : libpng-2:1.6.37-15.fc39.x86_64 76/249 Verifying : librabbitmq-0.13.0-3.fc39.x86_64 77/249 Verifying : librist-0.2.7-2.fc39.x86_64 78/249 Verifying : libsndfile-1.1.0-9.fc39.x86_64 79/249 Verifying : libstemmer-2.2.0-7.fc39.x86_64 80/249 Verifying : libtalloc-2.4.1-1.fc39.x86_64 81/249 Verifying : libtdb-1.4.9-1.fc39.x86_64 82/249 Verifying : libtevent-0.15.0-1.fc39.x86_64 83/249 Verifying : libthai-0.1.29-6.fc39.x86_64 84/249 Verifying : libtheora-1:1.1.1-34.fc39.x86_64 85/249 Verifying : libtiff-4.4.0-8.fc39.x86_64 86/249 Verifying : libtracker-sparql-3.6.0-1.fc39.x86_64 87/249 Verifying : libudfread-1.1.2-6.fc39.x86_64 88/249 Verifying : libunwind-1.7.0-0.2.rc2.fc39.x86_64 89/249 Verifying : libvdpau-1.5-4.fc39.x86_64 90/249 Verifying : libvisual-1:0.4.1-2.fc39.x86_64 91/249 Verifying : libvmaf-2.3.0-6.fc39.x86_64 92/249 Verifying : libvorbis-1:1.3.7-8.fc39.x86_64 93/249 Verifying : libwayland-client-1.22.0-2.fc39.x86_64 94/249 Verifying : libwayland-cursor-1.22.0-2.fc39.x86_64 95/249 Verifying : libwayland-egl-1.22.0-2.fc39.x86_64 96/249 Verifying : libwayland-server-1.22.0-2.fc39.x86_64 97/249 Verifying : libwebp-1.3.2-2.fc39.x86_64 98/249 Verifying : libxcb-1.13.1-12.fc39.x86_64 99/249 Verifying : libxshmfence-1.3-13.fc39.x86_64 100/249 Verifying : lpcnetfreedv-0.5-3.fc39.x86_64 101/249 Verifying : mpdecimal-2.5.1-7.fc39.x86_64 102/249 Verifying : mpg123-libs-1.31.3-2.fc39.x86_64 103/249 Verifying : mtdev-1.1.6-6.fc39.x86_64 104/249 Verifying : nettle-3.9.1-2.fc39.x86_64 105/249 Verifying : ocl-icd-2.3.2-2.fc39.x86_64 106/249 Verifying : opencore-amr-0.1.6-4.fc39.x86_64 107/249 Verifying : openpgm-5.2.122-32.fc39.x86_64 108/249 Verifying : opus-1.3.1-13.fc39.x86_64 109/249 Verifying : orc-0.4.33-3.fc39.x86_64 110/249 Verifying : pango-1.51.0-1.fc39.x86_64 111/249 Verifying : pcre2-utf16-10.42-1.fc39.2.x86_64 112/249 Verifying : pixman-0.42.2-2.fc39.x86_64 113/249 Verifying : pulseaudio-libs-16.1-5.fc39.x86_64 114/249 Verifying : python3-dbus-1.3.2-4.fc39.x86_64 115/249 Verifying : python3-packaging-23.1-4.fc39.noarch 116/249 Verifying : python3-rpm-generators-14-7.fc39.noarch 117/249 Verifying : shared-mime-info-2.2-4.fc39.x86_64 118/249 Verifying : snappy-1.1.10-2.fc39.x86_64 119/249 Verifying : soxr-0.1.3-14.fc39.x86_64 120/249 Verifying : speex-1.2.0-15.fc39.x86_64 121/249 Verifying : srt-libs-1.5.3-1.fc39.x86_64 122/249 Verifying : svt-av1-libs-1.4.1-3.fc39.x86_64 123/249 Verifying : tslib-1.22-9.fc39.x86_64 124/249 Verifying : twolame-libs-0.4.0-3.fc39.x86_64 125/249 Verifying : vapoursynth-libs-63-2.fc39.x86_64 126/249 Verifying : vo-amrwbenc-0.1.3-19.fc39.x86_64 127/249 Verifying : xcb-util-0.4.1-3.fc39.x86_64 128/249 Verifying : xcb-util-cursor-0.1.4-3.fc39.x86_64 129/249 Verifying : xcb-util-image-0.4.1-3.fc39.x86_64 130/249 Verifying : xcb-util-keysyms-0.4.1-3.fc39.x86_64 131/249 Verifying : xcb-util-renderutil-0.3.10-3.fc39.x86_64 132/249 Verifying : xcb-util-wm-0.4.2-3.fc39.x86_64 133/249 Verifying : xml-common-0.6.3-61.fc39.noarch 134/249 Verifying : xprop-1.2.5-4.fc39.x86_64 135/249 Verifying : xvidcore-1.3.7-10.fc39.x86_64 136/249 Verifying : zeromq-4.3.4-8.fc39.x86_64 137/249 Verifying : SDL2-2.28.5-1.fc39.x86_64 138/249 Verifying : alsa-lib-1.2.12-1.fc39.x86_64 139/249 Verifying : at-spi2-atk-2.50.2-1.fc39.x86_64 140/249 Verifying : at-spi2-core-2.50.2-1.fc39.x86_64 141/249 Verifying : atk-2.50.2-1.fc39.x86_64 142/249 Verifying : bluez-libs-5.77-1.fc39.x86_64 143/249 Verifying : cjson-1.7.17-1.fc39.x86_64 144/249 Verifying : cups-libs-1:2.4.10-7.fc39.x86_64 145/249 Verifying : dbus-broker-36-2.fc39.x86_64 146/249 Verifying : emacs-filesystem-1:29.4-2.fc39.noarch 147/249 Verifying : expat-2.6.3-1.fc39.x86_64 148/249 Verifying : fontconfig-2.14.2-6.fc39.x86_64 149/249 Verifying : glib2-2.78.6-1.fc39.x86_64 150/249 Verifying : gnutls-3.8.6-1.fc39.x86_64 151/249 Verifying : google-noto-fonts-common-20240101-1.fc39.noarch 152/249 Verifying : google-noto-sans-vf-fonts-20240101-1.fc39.noarch 153/249 Verifying : gssdp-1.6.3-1.fc39.x86_64 154/249 Verifying : gstreamer1-1.22.12-1.fc39.x86_64 155/249 Verifying : gstreamer1-plugins-bad-free-libs-1.22.12-1.fc39. 156/249 Verifying : gstreamer1-plugins-base-1.22.12-1.fc39.x86_64 157/249 Verifying : gtk-update-icon-cache-3.24.43-1.fc39.x86_64 158/249 Verifying : gtk3-3.24.43-1.fc39.x86_64 159/249 Verifying : gupnp-1.6.6-1.fc39.x86_64 160/249 Verifying : highway-1.1.0-1.fc39.x86_64 161/249 Verifying : hwdata-0.388-1.fc39.noarch 162/249 Verifying : libX11-1.8.9-1.fc39.x86_64 163/249 Verifying : libX11-common-1.8.9-1.fc39.noarch 164/249 Verifying : libX11-xcb-1.8.9-1.fc39.x86_64 165/249 Verifying : libXrandr-1.5.4-1.fc39.x86_64 166/249 Verifying : libaom-3.9.0-1.fc39.x86_64 167/249 Verifying : libavcodec-free-6.1.2-1.fc39.x86_64 168/249 Verifying : libavformat-free-6.1.2-1.fc39.x86_64 169/249 Verifying : libavutil-free-6.1.2-1.fc39.x86_64 170/249 Verifying : libcloudproviders-0.3.5-1.fc39.x86_64 171/249 Verifying : libdecor-0.2.2-1.fc39.x86_64 172/249 Verifying : libdrm-2.4.121-1.fc39.x86_64 173/249 Verifying : libgusb-0.4.9-1.fc39.x86_64 174/249 Verifying : libinput-1.25.0-5.fc39.x86_64 175/249 Verifying : libjxl-1:0.8.3-1.fc39.x86_64 176/249 Verifying : libldb-2.8.1-1.fc39.x86_64 177/249 Verifying : libopenmpt-0.7.8-1.fc39.x86_64 178/249 Verifying : libproxy-0.5.5-1.fc39.x86_64 179/249 Verifying : librsvg2-2.57.1-2.fc39.x86_64 180/249 Verifying : libseccomp-2.5.5-1.fc39.x86_64 181/249 Verifying : libsmbclient-2:4.19.8-1.fc39.x86_64 182/249 Verifying : libsodium-1.0.18-15.fc39.x86_64 183/249 Verifying : libsoup3-3.4.4-1.fc39.x86_64 184/249 Verifying : libswresample-free-6.1.2-1.fc39.x86_64 185/249 Verifying : libswscale-free-6.1.2-1.fc39.x86_64 186/249 Verifying : libusb1-1.0.27-2.fc39.x86_64 187/249 Verifying : libva-2.20.0-2.fc39.x86_64 188/249 Verifying : libvpl-1:2.13.0-1.fc39.x86_64 189/249 Verifying : libvpx-1.13.1-1.fc39.x86_64 190/249 Verifying : libwacom-2.10.0-1.fc39.x86_64 191/249 Verifying : libwacom-data-2.10.0-1.fc39.noarch 192/249 Verifying : libwbclient-2:4.19.8-1.fc39.x86_64 193/249 Verifying : libxkbcommon-1.6.0-1.fc39.x86_64 194/249 Verifying : libxkbcommon-x11-1.6.0-1.fc39.x86_64 195/249 Verifying : lmdb-libs-0.9.33-1.fc39.x86_64 196/249 Verifying : mbedtls-2.28.8-1.fc39.x86_64 197/249 Verifying : mesa-filesystem-23.3.6-1.fc39.x86_64 198/249 Verifying : mesa-libEGL-23.3.6-1.fc39.x86_64 199/249 Verifying : mesa-libGL-23.3.6-1.fc39.x86_64 200/249 Verifying : mesa-libgbm-23.3.6-1.fc39.x86_64 201/249 Verifying : mesa-libglapi-23.3.6-1.fc39.x86_64 202/249 Verifying : openjpeg2-2.5.2-1.fc39.x86_64 203/249 Verifying : pyproject-rpm-macros-1.15.1-1.fc39.noarch 204/249 Verifying : python-pip-wheel-23.2.1-2.fc39.noarch 205/249 Verifying : python-pyqt6-rpm-macros-6.6.1-5.fc39.noarch 206/249 Verifying : python-rpm-macros-3.12-8.fc39.noarch 207/249 Verifying : python3-3.12.7-1.fc39.x86_64 208/249 Verifying : python3-devel-3.12.7-1.fc39.x86_64 209/249 Verifying : python3-libs-3.12.7-1.fc39.x86_64 210/249 Verifying : python3-pyqt6-6.6.1-5.fc39.x86_64 211/249 Verifying : python3-pyqt6-base-6.6.1-5.fc39.x86_64 212/249 Verifying : python3-pyqt6-sip-13.6.0-1.fc39.x86_64 213/249 Verifying : python3-rpm-macros-3.12-8.fc39.noarch 214/249 Verifying : python3-setuptools-67.7.2-8.fc39.noarch 215/249 Verifying : qt6-qtbase-6.6.2-2.fc39.x86_64 216/249 Verifying : qt6-qtbase-common-6.6.2-2.fc39.noarch 217/249 Verifying : qt6-qtbase-gui-6.6.2-2.fc39.x86_64 218/249 Verifying : qt6-qtconnectivity-6.6.2-1.fc39.x86_64 219/249 Verifying : qt6-qtdeclarative-6.6.2-3.fc39.x86_64 220/249 Verifying : qt6-qtmultimedia-6.6.2-1.fc39.x86_64 221/249 Verifying : qt6-qtpdf-6.6.2-1.fc39.x86_64 222/249 Verifying : qt6-qtpositioning-6.6.2-1.fc39.x86_64 223/249 Verifying : qt6-qtquick3d-6.6.2-1.fc39.x86_64 224/249 Verifying : qt6-qtquicktimeline-6.6.2-1.fc39.x86_64 225/249 Verifying : qt6-qtremoteobjects-6.6.2-1.fc39.x86_64 226/249 Verifying : qt6-qtsensors-6.6.2-1.fc39.x86_64 227/249 Verifying : qt6-qtserialport-6.6.2-1.fc39.x86_64 228/249 Verifying : qt6-qtshadertools-6.6.2-1.fc39.x86_64 229/249 Verifying : qt6-qtspeech-6.6.2-1.fc39.x86_64 230/249 Verifying : qt6-qtsvg-6.6.2-1.fc39.x86_64 231/249 Verifying : qt6-qttools-common-6.6.2-1.fc39.noarch 232/249 Verifying : qt6-qttools-libs-designer-6.6.2-1.fc39.x86_64 233/249 Verifying : qt6-qttools-libs-help-6.6.2-1.fc39.x86_64 234/249 Verifying : qt6-qtwebchannel-6.6.2-1.fc39.x86_64 235/249 Verifying : qt6-qtwebsockets-6.6.2-1.fc39.x86_64 236/249 Verifying : rav1e-libs-0.7.1-4.fc39.x86_64 237/249 Verifying : rsvg-pixbuf-loader-2.57.1-2.fc39.x86_64 238/249 Verifying : samba-client-libs-2:4.19.8-1.fc39.x86_64 239/249 Verifying : samba-common-2:4.19.8-1.fc39.noarch 240/249 Verifying : samba-common-libs-2:4.19.8-1.fc39.x86_64 241/249 Verifying : systemd-254.18-1.fc39.x86_64 242/249 Verifying : systemd-pam-254.18-1.fc39.x86_64 243/249 Verifying : systemd-rpm-macros-254.18-1.fc39.noarch 244/249 Verifying : tzdata-2024a-2.fc39.noarch 245/249 Verifying : vulkan-loader-1.3.275.0-1.fc39.x86_64 246/249 Verifying : xkeyboard-config-2.40-1.fc39.noarch 247/249 Verifying : zimg-3.0.5-1.fc39.x86_64 248/249 Verifying : zvbi-0.2.42-1.fc39.x86_64 249/249 Installed: SDL2-2.28.5-1.fc39.x86_64 abattis-cantarell-vf-fonts-0.301-10.fc39.noarch adwaita-cursor-theme-45.0-1.fc39.noarch adwaita-icon-theme-45.0-1.fc39.noarch alsa-lib-1.2.12-1.fc39.x86_64 at-spi2-atk-2.50.2-1.fc39.x86_64 at-spi2-core-2.50.2-1.fc39.x86_64 atk-2.50.2-1.fc39.x86_64 avahi-libs-0.8-24.fc39.x86_64 bluez-libs-5.77-1.fc39.x86_64 cairo-1.18.0-1.fc39.x86_64 cairo-gobject-1.18.0-1.fc39.x86_64 cdparanoia-libs-10.2-42.fc39.x86_64 cjson-1.7.17-1.fc39.x86_64 codec2-1.2.0-2.fc39.x86_64 colord-libs-1.4.6-6.fc39.x86_64 cups-libs-1:2.4.10-7.fc39.x86_64 dbus-1:1.14.10-1.fc39.x86_64 dbus-broker-36-2.fc39.x86_64 dbus-common-1:1.14.10-1.fc39.noarch dbus-libs-1:1.14.10-1.fc39.x86_64 default-fonts-core-sans-4.0-9.fc39.noarch desktop-file-utils-0.26-9.fc39.x86_64 double-conversion-3.1.5-9.fc39.x86_64 duktape-2.7.0-5.fc39.x86_64 emacs-filesystem-1:29.4-2.fc39.noarch expat-2.6.3-1.fc39.x86_64 fdk-aac-free-2.0.0-11.fc39.x86_64 flac-libs-1.4.3-2.fc39.x86_64 fontconfig-2.14.2-6.fc39.x86_64 fonts-filesystem-1:2.0.5-12.fc39.noarch freetype-2.13.1-2.fc39.x86_64 fribidi-1.0.13-2.fc39.x86_64 game-music-emu-0.6.3-12.fc39.x86_64 gdk-pixbuf2-2.42.10-5.fc39.x86_64 gdk-pixbuf2-modules-2.42.10-5.fc39.x86_64 glib2-2.78.6-1.fc39.x86_64 glx-utils-9.0.0-3.fc39.x86_64 gnutls-3.8.6-1.fc39.x86_64 google-noto-fonts-common-20240101-1.fc39.noarch google-noto-sans-vf-fonts-20240101-1.fc39.noarch graphene-1.10.6-6.fc39.x86_64 graphite2-1.3.14-12.fc39.x86_64 gsm-1.0.22-3.fc39.x86_64 gssdp-1.6.3-1.fc39.x86_64 gstreamer1-1.22.12-1.fc39.x86_64 gstreamer1-plugins-bad-free-libs-1.22.12-1.fc39.x86_64 gstreamer1-plugins-base-1.22.12-1.fc39.x86_64 gtk-update-icon-cache-3.24.43-1.fc39.x86_64 gtk3-3.24.43-1.fc39.x86_64 gupnp-1.6.6-1.fc39.x86_64 gupnp-igd-1.6.0-2.fc39.x86_64 harfbuzz-8.2.1-2.fc39.x86_64 hicolor-icon-theme-0.17-16.fc39.noarch highway-1.1.0-1.fc39.x86_64 hwdata-0.388-1.fc39.noarch ilbc-3.0.4-7.fc39.x86_64 iso-codes-4.15.0-2.fc39.noarch jbigkit-libs-2.1-26.fc39.x86_64 json-glib-1.8.0-1.fc39.x86_64 kmod-libs-30-6.fc39.x86_64 lame-libs-3.100-15.fc39.x86_64 lcms2-2.15-2.fc39.x86_64 libICE-1.0.10-11.fc39.x86_64 libSM-1.2.3-13.fc39.x86_64 libX11-1.8.9-1.fc39.x86_64 libX11-common-1.8.9-1.fc39.noarch libX11-xcb-1.8.9-1.fc39.x86_64 libXau-1.0.11-3.fc39.x86_64 libXcomposite-0.4.5-10.fc39.x86_64 libXcursor-1.2.1-4.fc39.x86_64 libXdamage-1.1.5-10.fc39.x86_64 libXext-1.3.5-3.fc39.x86_64 libXfixes-6.0.0-6.fc39.x86_64 libXft-2.3.8-3.fc39.x86_64 libXi-1.8.1-2.fc39.x86_64 libXinerama-1.1.5-3.fc39.x86_64 libXrandr-1.5.4-1.fc39.x86_64 libXrender-0.9.11-3.fc39.x86_64 libXtst-1.2.4-3.fc39.x86_64 libXv-1.0.11-19.fc39.x86_64 libXxf86vm-1.1.5-3.fc39.x86_64 libaom-3.9.0-1.fc39.x86_64 libasyncns-0.8-25.fc39.x86_64 libavcodec-free-6.1.2-1.fc39.x86_64 libavformat-free-6.1.2-1.fc39.x86_64 libavutil-free-6.1.2-1.fc39.x86_64 libb2-0.98.1-9.fc39.x86_64 libbluray-1.3.4-3.fc39.x86_64 libchromaprint-1.5.1-13.fc39.x86_64 libcloudproviders-0.3.5-1.fc39.x86_64 libdatrie-0.2.13-7.fc39.x86_64 libdav1d-1.2.1-2.fc39.x86_64 libdecor-0.2.2-1.fc39.x86_64 libdrm-2.4.121-1.fc39.x86_64 libepoxy-1.5.10-4.fc39.x86_64 libevdev-1.13.1-2.fc39.x86_64 libgcrypt-1.10.2-2.fc39.x86_64 libglvnd-1:1.7.0-1.fc39.x86_64 libglvnd-egl-1:1.7.0-1.fc39.x86_64 libglvnd-glx-1:1.7.0-1.fc39.x86_64 libglvnd-opengl-1:1.7.0-1.fc39.x86_64 libgpg-error-1.47-2.fc39.x86_64 libgudev-238-2.fc39.x86_64 libgusb-0.4.9-1.fc39.x86_64 libicu-73.2-2.fc39.x86_64 libinput-1.25.0-5.fc39.x86_64 libjpeg-turbo-2.1.4-3.fc39.x86_64 libjxl-1:0.8.3-1.fc39.x86_64 libldb-2.8.1-1.fc39.x86_64 liblerc-4.0.0-4.fc39.x86_64 libmodplug-1:0.8.9.0-17.fc39.x86_64 libnice-0.1.21-4.fc39.x86_64 libogg-2:1.3.5-6.fc39.x86_64 libopenmpt-0.7.8-1.fc39.x86_64 libpciaccess-0.16-9.fc39.x86_64 libpng-2:1.6.37-15.fc39.x86_64 libproxy-0.5.5-1.fc39.x86_64 librabbitmq-0.13.0-3.fc39.x86_64 librist-0.2.7-2.fc39.x86_64 librsvg2-2.57.1-2.fc39.x86_64 libseccomp-2.5.5-1.fc39.x86_64 libsmbclient-2:4.19.8-1.fc39.x86_64 libsndfile-1.1.0-9.fc39.x86_64 libsodium-1.0.18-15.fc39.x86_64 libsoup3-3.4.4-1.fc39.x86_64 libstemmer-2.2.0-7.fc39.x86_64 libswresample-free-6.1.2-1.fc39.x86_64 libswscale-free-6.1.2-1.fc39.x86_64 libtalloc-2.4.1-1.fc39.x86_64 libtdb-1.4.9-1.fc39.x86_64 libtevent-0.15.0-1.fc39.x86_64 libthai-0.1.29-6.fc39.x86_64 libtheora-1:1.1.1-34.fc39.x86_64 libtiff-4.4.0-8.fc39.x86_64 libtracker-sparql-3.6.0-1.fc39.x86_64 libudfread-1.1.2-6.fc39.x86_64 libunwind-1.7.0-0.2.rc2.fc39.x86_64 libusb1-1.0.27-2.fc39.x86_64 libva-2.20.0-2.fc39.x86_64 libvdpau-1.5-4.fc39.x86_64 libvisual-1:0.4.1-2.fc39.x86_64 libvmaf-2.3.0-6.fc39.x86_64 libvorbis-1:1.3.7-8.fc39.x86_64 libvpl-1:2.13.0-1.fc39.x86_64 libvpx-1.13.1-1.fc39.x86_64 libwacom-2.10.0-1.fc39.x86_64 libwacom-data-2.10.0-1.fc39.noarch libwayland-client-1.22.0-2.fc39.x86_64 libwayland-cursor-1.22.0-2.fc39.x86_64 libwayland-egl-1.22.0-2.fc39.x86_64 libwayland-server-1.22.0-2.fc39.x86_64 libwbclient-2:4.19.8-1.fc39.x86_64 libwebp-1.3.2-2.fc39.x86_64 libxcb-1.13.1-12.fc39.x86_64 libxkbcommon-1.6.0-1.fc39.x86_64 libxkbcommon-x11-1.6.0-1.fc39.x86_64 libxshmfence-1.3-13.fc39.x86_64 lmdb-libs-0.9.33-1.fc39.x86_64 lpcnetfreedv-0.5-3.fc39.x86_64 mbedtls-2.28.8-1.fc39.x86_64 mesa-filesystem-23.3.6-1.fc39.x86_64 mesa-libEGL-23.3.6-1.fc39.x86_64 mesa-libGL-23.3.6-1.fc39.x86_64 mesa-libgbm-23.3.6-1.fc39.x86_64 mesa-libglapi-23.3.6-1.fc39.x86_64 mpdecimal-2.5.1-7.fc39.x86_64 mpg123-libs-1.31.3-2.fc39.x86_64 mtdev-1.1.6-6.fc39.x86_64 nettle-3.9.1-2.fc39.x86_64 ocl-icd-2.3.2-2.fc39.x86_64 opencore-amr-0.1.6-4.fc39.x86_64 openjpeg2-2.5.2-1.fc39.x86_64 openpgm-5.2.122-32.fc39.x86_64 opus-1.3.1-13.fc39.x86_64 orc-0.4.33-3.fc39.x86_64 pango-1.51.0-1.fc39.x86_64 pcre2-utf16-10.42-1.fc39.2.x86_64 pixman-0.42.2-2.fc39.x86_64 pulseaudio-libs-16.1-5.fc39.x86_64 pyproject-rpm-macros-1.15.1-1.fc39.noarch python-pip-wheel-23.2.1-2.fc39.noarch python-pyqt6-rpm-macros-6.6.1-5.fc39.noarch python-rpm-macros-3.12-8.fc39.noarch python3-3.12.7-1.fc39.x86_64 python3-dbus-1.3.2-4.fc39.x86_64 python3-devel-3.12.7-1.fc39.x86_64 python3-libs-3.12.7-1.fc39.x86_64 python3-packaging-23.1-4.fc39.noarch python3-pyqt6-6.6.1-5.fc39.x86_64 python3-pyqt6-base-6.6.1-5.fc39.x86_64 python3-pyqt6-sip-13.6.0-1.fc39.x86_64 python3-rpm-generators-14-7.fc39.noarch python3-rpm-macros-3.12-8.fc39.noarch python3-setuptools-67.7.2-8.fc39.noarch qt6-qtbase-6.6.2-2.fc39.x86_64 qt6-qtbase-common-6.6.2-2.fc39.noarch qt6-qtbase-gui-6.6.2-2.fc39.x86_64 qt6-qtconnectivity-6.6.2-1.fc39.x86_64 qt6-qtdeclarative-6.6.2-3.fc39.x86_64 qt6-qtmultimedia-6.6.2-1.fc39.x86_64 qt6-qtpdf-6.6.2-1.fc39.x86_64 qt6-qtpositioning-6.6.2-1.fc39.x86_64 qt6-qtquick3d-6.6.2-1.fc39.x86_64 qt6-qtquicktimeline-6.6.2-1.fc39.x86_64 qt6-qtremoteobjects-6.6.2-1.fc39.x86_64 qt6-qtsensors-6.6.2-1.fc39.x86_64 qt6-qtserialport-6.6.2-1.fc39.x86_64 qt6-qtshadertools-6.6.2-1.fc39.x86_64 qt6-qtspeech-6.6.2-1.fc39.x86_64 qt6-qtsvg-6.6.2-1.fc39.x86_64 qt6-qttools-common-6.6.2-1.fc39.noarch qt6-qttools-libs-designer-6.6.2-1.fc39.x86_64 qt6-qttools-libs-help-6.6.2-1.fc39.x86_64 qt6-qtwebchannel-6.6.2-1.fc39.x86_64 qt6-qtwebsockets-6.6.2-1.fc39.x86_64 rav1e-libs-0.7.1-4.fc39.x86_64 rsvg-pixbuf-loader-2.57.1-2.fc39.x86_64 samba-client-libs-2:4.19.8-1.fc39.x86_64 samba-common-2:4.19.8-1.fc39.noarch samba-common-libs-2:4.19.8-1.fc39.x86_64 shared-mime-info-2.2-4.fc39.x86_64 snappy-1.1.10-2.fc39.x86_64 soxr-0.1.3-14.fc39.x86_64 speex-1.2.0-15.fc39.x86_64 srt-libs-1.5.3-1.fc39.x86_64 svt-av1-libs-1.4.1-3.fc39.x86_64 systemd-254.18-1.fc39.x86_64 systemd-pam-254.18-1.fc39.x86_64 systemd-rpm-macros-254.18-1.fc39.noarch tslib-1.22-9.fc39.x86_64 twolame-libs-0.4.0-3.fc39.x86_64 tzdata-2024a-2.fc39.noarch vapoursynth-libs-63-2.fc39.x86_64 vo-amrwbenc-0.1.3-19.fc39.x86_64 vulkan-loader-1.3.275.0-1.fc39.x86_64 xcb-util-0.4.1-3.fc39.x86_64 xcb-util-cursor-0.1.4-3.fc39.x86_64 xcb-util-image-0.4.1-3.fc39.x86_64 xcb-util-keysyms-0.4.1-3.fc39.x86_64 xcb-util-renderutil-0.3.10-3.fc39.x86_64 xcb-util-wm-0.4.2-3.fc39.x86_64 xkeyboard-config-2.40-1.fc39.noarch xml-common-0.6.3-61.fc39.noarch xprop-1.2.5-4.fc39.x86_64 xvidcore-1.3.7-10.fc39.x86_64 zeromq-4.3.4-8.fc39.x86_64 zimg-3.0.5-1.fc39.x86_64 zvbi-0.2.42-1.fc39.x86_64 Complete! Finish: build setup for zapzap-5.3.8-1.fc39.src.rpm Start: rpmbuild zapzap-5.3.8-1.fc39.src.rpm warning: source_date_epoch_from_changelog set but %changelog is missing Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.ykX9JK + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf zapzap-5.3.8 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/5.3.8.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd zapzap-5.3.8 + rm -rf /builddir/build/BUILD/zapzap-5.3.8-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/zapzap-5.3.8-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.v5YoKv + 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 -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 -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 -Cstrip=none -Cforce-frame-pointers=yes -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-5.3.8 + 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.12/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/__init__.py -> build/lib/zapzap copying zapzap/__main__.py -> build/lib/zapzap creating build/lib/zapzap/controllers copying zapzap/controllers/SingleApplication.py -> build/lib/zapzap/controllers copying zapzap/controllers/card_user.py -> build/lib/zapzap/controllers copying zapzap/controllers/download_popup.py -> build/lib/zapzap/controllers copying zapzap/controllers/drawer.py -> build/lib/zapzap/controllers copying zapzap/controllers/home.py -> build/lib/zapzap/controllers copying zapzap/controllers/main_window.py -> build/lib/zapzap/controllers copying zapzap/controllers/open_chat_popup.py -> build/lib/zapzap/controllers copying zapzap/controllers/qtoaster_donation.py -> build/lib/zapzap/controllers copying zapzap/controllers/settings.py -> build/lib/zapzap/controllers copying zapzap/controllers/user_container.py -> build/lib/zapzap/controllers creating build/lib/zapzap/controllers/main_window_components copying zapzap/controllers/main_window_components/builder_icon.py -> build/lib/zapzap/controllers/main_window_components copying zapzap/controllers/main_window_components/tray_icon.py -> build/lib/zapzap/controllers/main_window_components creating build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/about.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/account.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/advanced.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/donations.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/general.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/network.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/notifications.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/personalization.py -> build/lib/zapzap/controllers/settings_pages copying zapzap/controllers/settings_pages/tools.py -> build/lib/zapzap/controllers/settings_pages creating build/lib/zapzap/engine copying zapzap/engine/browser.py -> build/lib/zapzap/engine copying zapzap/engine/whatsapp.py -> build/lib/zapzap/engine creating build/lib/zapzap/services copying zapzap/services/dbus_notify.py -> build/lib/zapzap/services copying zapzap/services/dbus_theme.py -> build/lib/zapzap/services copying zapzap/services/portal_desktop.py -> build/lib/zapzap/services copying zapzap/services/qtoaster.py -> build/lib/zapzap/services copying zapzap/services/spellCheckLanguages.py -> build/lib/zapzap/services creating build/lib/zapzap/theme copying zapzap/theme/builder_icon.py -> build/lib/zapzap/theme copying zapzap/theme/icons.py -> build/lib/zapzap/theme copying zapzap/theme/style.py -> build/lib/zapzap/theme copying zapzap/theme/zap_themes.py -> build/lib/zapzap/theme creating build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/menu_home.py -> build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/popup.py -> build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/qwidgets.py -> build/lib/zapzap/theme/style_components copying zapzap/theme/style_components/settings.py -> build/lib/zapzap/theme/style_components creating build/lib/zapzap/view copying zapzap/view/about_page.py -> build/lib/zapzap/view copying zapzap/view/account_page.py -> build/lib/zapzap/view copying zapzap/view/advanced_page.py -> build/lib/zapzap/view copying zapzap/view/card_user.py -> build/lib/zapzap/view copying zapzap/view/donations_page.py -> build/lib/zapzap/view copying zapzap/view/downloadPopup.py -> build/lib/zapzap/view copying zapzap/view/drawer.py -> build/lib/zapzap/view copying zapzap/view/general_page.py -> build/lib/zapzap/view copying zapzap/view/home.py -> build/lib/zapzap/view copying zapzap/view/main_window.py -> build/lib/zapzap/view copying zapzap/view/network_page.py -> build/lib/zapzap/view copying zapzap/view/notifications_page.py -> build/lib/zapzap/view copying zapzap/view/openChatPopup.py -> build/lib/zapzap/view copying zapzap/view/personalization_page.py -> build/lib/zapzap/view copying zapzap/view/qtoaster_donation.py -> build/lib/zapzap/view copying zapzap/view/settings.py -> build/lib/zapzap/view creating build/lib/zapzap/model copying zapzap/model/db.py -> build/lib/zapzap/model copying zapzap/model/user.py -> build/lib/zapzap/model running egg_info creating zapzap.egg-info writing zapzap.egg-info/PKG-INFO writing dependency_links to zapzap.egg-info/dependency_links.txt writing entry points to zapzap.egg-info/entry_points.txt writing top-level names to zapzap.egg-info/top_level.txt writing manifest file 'zapzap.egg-info/SOURCES.txt' reading manifest file 'zapzap.egg-info/SOURCES.txt' adding license file 'LICENSE' writing manifest file 'zapzap.egg-info/SOURCES.txt' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py: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.12/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.12/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.12/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.12/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.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'zapzap.assets.icons.tray' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.tray' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.tray' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.tray' to be distributed and are already explicitly excluding 'zapzap.assets.icons.tray' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py: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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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) creating build/lib/zapzap/assets creating build/lib/zapzap/assets/icons creating build/lib/zapzap/assets/icons/app creating build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/about.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/appearance.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/bell-ringing.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/bell-slash.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/border.png -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/borderDialog.png -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/chat.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_checked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_checked_disabled.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_indeterminate.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_indeterminate_disabled.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_unchecked.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/checkbox_unchecked_disabled.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/donations.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/expand_more.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/eye-slash.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/eye.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/gear-six.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/manage_accounts.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/network.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/notifications.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/phone-plus.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/sign-out.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/system.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/transparent.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/trash.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/user-plus.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/user.svg -> build/lib/zapzap/assets/icons/app/dark copying zapzap/assets/icons/app/dark/wrench.svg -> build/lib/zapzap/assets/icons/app/dark creating build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/about.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/appearance.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/bell-ringing.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/bell-slash.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/border.png -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/borderDialog.png -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/chat.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_checked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_checked_disabled.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_indeterminate.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_indeterminate_disabled.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_unchecked.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/checkbox_unchecked_disabled.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/donations.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/expand_more.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/eye-slash.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/eye.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/gear-six.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/manage_accounts.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/network.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/notifications.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/phone-plus.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/sign-out.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/system.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/transparent.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/trash.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/user-plus.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/user.svg -> build/lib/zapzap/assets/icons/app/light copying zapzap/assets/icons/app/light/wrench.svg -> build/lib/zapzap/assets/icons/app/light creating build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/PayPal.png -> build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/kofi.svg -> build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/pix.png -> build/lib/zapzap/assets/icons/banners copying zapzap/assets/icons/banners/sponsor.svg -> build/lib/zapzap/assets/icons/banners creating build/lib/zapzap/assets/icons/titlebar_buttons creating build/lib/zapzap/assets/icons/titlebar_buttons/default creating build/lib/zapzap/assets/icons/titlebar_buttons/default/dark copying zapzap/assets/icons/titlebar_buttons/default/dark/btn_close.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/dark creating build/lib/zapzap/assets/icons/titlebar_buttons/default/light copying zapzap/assets/icons/titlebar_buttons/default/light/btn_close.svg -> build/lib/zapzap/assets/icons/titlebar_buttons/default/light creating build/lib/zapzap/assets/icons/tray copying zapzap/assets/icons/tray/default_normal.svg -> build/lib/zapzap/assets/icons/tray copying zapzap/assets/icons/tray/model.svg -> build/lib/zapzap/assets/icons/tray copying zapzap/assets/icons/tray/simbolic_model.svg -> build/lib/zapzap/assets/icons/tray creating build/lib/zapzap/po creating build/lib/zapzap/po/am creating build/lib/zapzap/po/am/LC_MESSAGES copying zapzap/po/am/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/am/LC_MESSAGES creating build/lib/zapzap/po/ar creating build/lib/zapzap/po/ar/LC_MESSAGES copying zapzap/po/ar/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ar/LC_MESSAGES creating build/lib/zapzap/po/ca creating build/lib/zapzap/po/ca/LC_MESSAGES copying zapzap/po/ca/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/ca/LC_MESSAGES creating build/lib/zapzap/po/cs creating build/lib/zapzap/po/cs/LC_MESSAGES copying zapzap/po/cs/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/cs/LC_MESSAGES creating build/lib/zapzap/po/da creating build/lib/zapzap/po/da/LC_MESSAGES copying zapzap/po/da/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/da/LC_MESSAGES creating build/lib/zapzap/po/de creating build/lib/zapzap/po/de/LC_MESSAGES copying zapzap/po/de/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/de/LC_MESSAGES creating build/lib/zapzap/po/el creating build/lib/zapzap/po/el/LC_MESSAGES copying zapzap/po/el/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/el/LC_MESSAGES creating build/lib/zapzap/po/eo creating build/lib/zapzap/po/eo/LC_MESSAGES copying zapzap/po/eo/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/eo/LC_MESSAGES creating build/lib/zapzap/po/es creating build/lib/zapzap/po/es/LC_MESSAGES copying zapzap/po/es/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/es/LC_MESSAGES creating build/lib/zapzap/po/eu creating build/lib/zapzap/po/eu/LC_MESSAGES copying zapzap/po/eu/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/eu/LC_MESSAGES creating build/lib/zapzap/po/fa creating build/lib/zapzap/po/fa/LC_MESSAGES copying zapzap/po/fa/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fa/LC_MESSAGES creating build/lib/zapzap/po/fi creating build/lib/zapzap/po/fi/LC_MESSAGES copying zapzap/po/fi/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fi/LC_MESSAGES creating build/lib/zapzap/po/fr creating build/lib/zapzap/po/fr/LC_MESSAGES copying zapzap/po/fr/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fr/LC_MESSAGES creating build/lib/zapzap/po/fy creating build/lib/zapzap/po/fy/LC_MESSAGES copying zapzap/po/fy/LC_MESSAGES/zapzap.mo -> build/lib/zapzap/po/fy/LC_MESSAGES creating build/lib/zapzap/po/gl creating build/lib/zapzap/po/gl/LC_MESSAGES /usr/lib/python3.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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/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 + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.VsY9t5 ++ dirname /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/zapzap-5.3.8-1.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 -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 -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 -Cstrip=none -Cforce-frame-pointers=yes -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-5.3.8 + /usr/bin/python3 setup.py install --root /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64 /usr/lib/python3.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'zapzap.assets.icons.tray' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'zapzap.assets.icons.tray' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'zapzap.assets.icons.tray' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'zapzap.assets.icons.tray' to be distributed and are already explicitly excluding 'zapzap.assets.icons.tray' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py: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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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) running install_lib creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12 creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap copying build/lib/zapzap/__init__.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap copying build/lib/zapzap/__main__.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/SingleApplication.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/card_user.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/download_popup.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/drawer.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/home.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/main_window.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/open_chat_popup.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/qtoaster_donation.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/settings.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers copying build/lib/zapzap/controllers/user_container.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/builder_icon.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/main_window_components copying build/lib/zapzap/controllers/main_window_components/tray_icon.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/main_window_components creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/about.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/account.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/advanced.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/donations.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/general.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/network.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/notifications.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/personalization.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages copying build/lib/zapzap/controllers/settings_pages/tools.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/engine copying build/lib/zapzap/engine/browser.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/engine copying build/lib/zapzap/engine/whatsapp.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/engine creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services copying build/lib/zapzap/services/dbus_notify.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services copying build/lib/zapzap/services/dbus_theme.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services copying build/lib/zapzap/services/portal_desktop.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services copying build/lib/zapzap/services/qtoaster.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services copying build/lib/zapzap/services/spellCheckLanguages.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme copying build/lib/zapzap/theme/builder_icon.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme copying build/lib/zapzap/theme/icons.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme copying build/lib/zapzap/theme/style.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme copying build/lib/zapzap/theme/zap_themes.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/menu_home.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/popup.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/qwidgets.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components copying build/lib/zapzap/theme/style_components/settings.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/about_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/account_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/advanced_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/card_user.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/donations_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/downloadPopup.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/drawer.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/general_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/home.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/main_window.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/network_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/notifications_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/openChatPopup.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/personalization_page.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/qtoaster_donation.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view copying build/lib/zapzap/view/settings.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/model copying build/lib/zapzap/model/db.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/model copying build/lib/zapzap/model/user.py -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/model creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/about.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/appearance.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/bell-ringing.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/bell-slash.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/border.png -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/borderDialog.png -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/chat.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_checked.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_checked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_indeterminate.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_indeterminate_disabled.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/checkbox_unchecked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/donations.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/expand_more.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/eye-slash.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/eye.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/gear-six.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/manage_accounts.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/network.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/notifications.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/phone-plus.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/sign-out.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/system.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/transparent.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/trash.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/user-plus.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/user.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark copying build/lib/zapzap/assets/icons/app/dark/wrench.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/dark creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/about.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/appearance.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/bell-ringing.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/bell-slash.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/border.png -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/borderDialog.png -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/chat.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_checked.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_checked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_indeterminate.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_indeterminate_disabled.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_unchecked.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/checkbox_unchecked_disabled.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/donations.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/expand_more.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/eye-slash.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/eye.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/gear-six.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/manage_accounts.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/network.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/notifications.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/phone-plus.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/sign-out.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/system.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/transparent.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/trash.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/user-plus.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/user.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light copying build/lib/zapzap/assets/icons/app/light/wrench.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/app/light creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/PayPal.png -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/kofi.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/pix.png -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/banners copying build/lib/zapzap/assets/icons/banners/sponsor.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/banners creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/titlebar_buttons creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/titlebar_buttons/default creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/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-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/titlebar_buttons/default/dark creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/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-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/titlebar_buttons/default/light creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/tray copying build/lib/zapzap/assets/icons/tray/default_normal.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/tray copying build/lib/zapzap/assets/icons/tray/model.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/tray copying build/lib/zapzap/assets/icons/tray/simbolic_model.svg -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/assets/icons/tray creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/am creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/am/LC_MESSAGES copying build/lib/zapzap/po/am/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/am/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ar creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ar/LC_MESSAGES copying build/lib/zapzap/po/ar/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ca creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ca/LC_MESSAGES copying build/lib/zapzap/po/ca/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/cs creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/cs/LC_MESSAGES copying build/lib/zapzap/po/cs/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/da creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/da/LC_MESSAGES copying build/lib/zapzap/po/da/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/da/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/de creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/de/LC_MESSAGES copying build/lib/zapzap/po/de/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/de/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/el creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/el/LC_MESSAGES copying build/lib/zapzap/po/el/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/el/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/eo creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/eo/LC_MESSAGES copying build/lib/zapzap/po/eo/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/es creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/es/LC_MESSAGES copying build/lib/zapzap/po/es/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/es/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/eu creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/eu/LC_MESSAGES copying build/lib/zapzap/po/eu/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fa creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fa/LC_MESSAGES copying build/lib/zapzap/po/fa/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fi creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fi/LC_MESSAGES copying build/lib/zapzap/po/fi/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fr creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fr/LC_MESSAGES copying build/lib/zapzap/po/fr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fy creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fy/LC_MESSAGES copying build/lib/zapzap/po/fy/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/gl creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/gl/LC_MESSAGES copying build/lib/zapzap/po/gl/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/he creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/he/LC_MESSAGES copying build/lib/zapzap/po/he/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/he/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hi creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hi/LC_MESSAGES copying build/lib/zapzap/po/hi/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hr creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hr/LC_MESSAGES copying build/lib/zapzap/po/hr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hu creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hu/LC_MESSAGES copying build/lib/zapzap/po/hu/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/id creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/id/LC_MESSAGES copying build/lib/zapzap/po/id/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/id/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/it creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/it/LC_MESSAGES copying build/lib/zapzap/po/it/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/it/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ja creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ja/LC_MESSAGES copying build/lib/zapzap/po/ja/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ka creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ka/LC_MESSAGES copying build/lib/zapzap/po/ka/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/kmr creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/kmr/LC_MESSAGES copying build/lib/zapzap/po/kmr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/kmr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/kn creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/kn/LC_MESSAGES copying build/lib/zapzap/po/kn/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ko creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ko/LC_MESSAGES /usr/lib/python3.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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.12/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 build/lib/zapzap/po/ko/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/lt creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/lt/LC_MESSAGES copying build/lib/zapzap/po/lt/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/lv creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/lv/LC_MESSAGES copying build/lib/zapzap/po/lv/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/nb_NO creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/nb_NO/LC_MESSAGES copying build/lib/zapzap/po/nb_NO/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/nb_NO/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/nl creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/nl/LC_MESSAGES copying build/lib/zapzap/po/nl/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/oc creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/oc/LC_MESSAGES copying build/lib/zapzap/po/oc/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/oc/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pl creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pl/LC_MESSAGES copying build/lib/zapzap/po/pl/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pt creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pt/LC_MESSAGES copying build/lib/zapzap/po/pt/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pt_BR creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pt_BR/LC_MESSAGES copying build/lib/zapzap/po/pt_BR/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ru creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ru/LC_MESSAGES copying build/lib/zapzap/po/ru/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/si creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/si/LC_MESSAGES copying build/lib/zapzap/po/si/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/si/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sk creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sk/LC_MESSAGES copying build/lib/zapzap/po/sk/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sr creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sr/LC_MESSAGES copying build/lib/zapzap/po/sr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sv creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sv/LC_MESSAGES copying build/lib/zapzap/po/sv/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/tr creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/tr/LC_MESSAGES copying build/lib/zapzap/po/tr/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/uk creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/uk/LC_MESSAGES copying build/lib/zapzap/po/uk/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/zh_CN creating /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/zh_CN/LC_MESSAGES copying build/lib/zapzap/po/zh_CN/LC_MESSAGES/zapzap.mo -> /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/po/zh_CN/LC_MESSAGES byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/__main__.py to __main__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/SingleApplication.py to SingleApplication.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/card_user.py to card_user.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/download_popup.py to download_popup.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/drawer.py to drawer.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/home.py to home.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/main_window.py to main_window.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/open_chat_popup.py to open_chat_popup.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/qtoaster_donation.py to qtoaster_donation.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings.py to settings.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/user_container.py to user_container.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/main_window_components/builder_icon.py to builder_icon.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/main_window_components/tray_icon.py to tray_icon.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/about.py to about.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/account.py to account.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/advanced.py to advanced.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/donations.py to donations.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/general.py to general.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/network.py to network.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/notifications.py to notifications.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/personalization.py to personalization.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/controllers/settings_pages/tools.py to tools.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/engine/browser.py to browser.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/engine/whatsapp.py to whatsapp.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services/dbus_notify.py to dbus_notify.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services/dbus_theme.py to dbus_theme.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services/portal_desktop.py to portal_desktop.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services/qtoaster.py to qtoaster.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/services/spellCheckLanguages.py to spellCheckLanguages.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/builder_icon.py to builder_icon.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/icons.py to icons.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style.py to style.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/zap_themes.py to zap_themes.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components/menu_home.py to menu_home.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components/popup.py to popup.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components/qwidgets.py to qwidgets.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/theme/style_components/settings.py to settings.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/about_page.py to about_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/account_page.py to account_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/advanced_page.py to advanced_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/card_user.py to card_user.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/donations_page.py to donations_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/downloadPopup.py to downloadPopup.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/drawer.py to drawer.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/general_page.py to general_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/home.py to home.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/main_window.py to main_window.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/network_page.py to network_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/notifications_page.py to notifications_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/openChatPopup.py to openChatPopup.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/personalization_page.py to personalization_page.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/qtoaster_donation.py to qtoaster_donation.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/view/settings.py to settings.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/model/db.py to db.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap/model/user.py to user.cpython-312.pyc running install_egg_info Copying zapzap.egg-info to /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/lib/python3.12/site-packages/zapzap-5.3-py3.12.egg-info running install_scripts Installing zapzap script to /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/bin + mkdir -p /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/applications + mkdir -p /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/icons/hicolor/scalable/apps/ + cp -R share/applications/com.rtosta.zapzap.desktop /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/applications/com.rtosta.zapzap.desktop + cp -R share/icons/com.rtosta.zapzap.svg /builddir/build/BUILDROOT/zapzap-5.3.8-1.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 5.3.8-1.fc39 --unique-debug-suffix -5.3.8-1.fc39.x86_64 --unique-debug-src-base zapzap-5.3.8-1.fc39.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/zapzap-5.3.8 find-debuginfo: starting Extracting debug info from 0 files Creating .debug symlinks for symlinks to ELF files find: ‘debug’: No such file or directory find-debuginfo: done + /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-5.3.8-1.fc39.x86_64/usr/lib/python3.12 using python3.12 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.kXm1wL + 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 -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 -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 Processing files: zapzap-5.3.8-1.fc39.noarch + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -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-5.3.8 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.OFx40G + umask 022 + cd /builddir/build/BUILD + cd zapzap-5.3.8 + DOCDIR=/builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/doc/zapzap + export LC_ALL= + LC_ALL= + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/doc/zapzap + cp -pr /builddir/build/BUILD/zapzap-5.3.8/README.md /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/doc/zapzap + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.f50ieS + umask 022 + cd /builddir/build/BUILD + cd zapzap-5.3.8 + LICENSEDIR=/builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/licenses/zapzap + export LC_ALL= + LC_ALL= + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64/usr/share/licenses/zapzap + cp -pr /builddir/build/BUILD/zapzap-5.3.8/LICENSE /builddir/build/BUILDROOT/zapzap-5.3.8-1.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.12dist(zapzap) = 5.3 python3dist(zapzap) = 5.3 zapzap = 5.3.8-1.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.12 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64 Wrote: /builddir/build/RPMS/zapzap-5.3.8-1.fc39.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.PbaSWq + umask 022 + cd /builddir/build/BUILD + cd zapzap-5.3.8 + /usr/bin/rm -rf /builddir/build/BUILDROOT/zapzap-5.3.8-1.fc39.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.uLFDIT + umask 022 + cd /builddir/build/BUILD + rm -rf /builddir/build/BUILD/zapzap-5.3.8-SPECPARTS + rm -rf zapzap-5.3.8 zapzap-5.3.8.gemspec + RPM_EC=0 ++ jobs -p + exit 0 RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing Finish: rpmbuild zapzap-5.3.8-1.fc39.src.rpm Finish: build phase for zapzap-5.3.8-1.fc39.src.rpm INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-39-x86_64-1729951987.459697/root/var/log/dnf.log /var/lib/mock/fedora-39-x86_64-1729951987.459697/root/var/log/dnf.librepo.log /var/lib/mock/fedora-39-x86_64-1729951987.459697/root/var/log/dnf.rpm.log INFO: Done(/var/lib/copr-rpmbuild/results/zapzap-5.3.8-1.fc39.src.rpm) Config(child) 0 minutes 36 seconds INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results INFO: Cleaning up build root ('cleanup_on_success=True') Start: clean chroot INFO: unmounting tmpfs. Finish: clean chroot Finish: run Running FedoraReview tool Running: fedora-review --no-colors --prebuilt --rpm-spec --name zapzap --mock-config /var/lib/copr-rpmbuild/results/configs/child.cfg cmd: ['fedora-review', '--no-colors', '--prebuilt', '--rpm-spec', '--name', 'zapzap', '--mock-config', '/var/lib/copr-rpmbuild/results/configs/child.cfg'] cwd: /var/lib/copr-rpmbuild/results rc: 1 stdout: stderr: INFO: Processing local files: zapzap INFO: Getting .spec and .srpm Urls from : Local files in /var/lib/copr-rpmbuild/results INFO: --> SRPM url: file:///var/lib/copr-rpmbuild/results/zapzap-5.3.8-1.fc39.src.rpm INFO: Using review directory: /var/lib/copr-rpmbuild/results/zapzap WARNING: DNF4 command failed, retrying, attempt #2, sleeping 10s WARNING: No disttag found in prebuilt packages INFO: Use --define DISTTAG to set proper dist. e. g. --define DISTTAG fc21. ERROR: 'No disttag in package and no DISTTAG flag. Use --define DISTTAG to set proper dist e. g., --define DISTTAG=fc21.' (logs in /var/lib/copr-rpmbuild/results/cache/fedora-review.log) Fedora review failed err: INFO: Processing local files: zapzap INFO: Getting .spec and .srpm Urls from : Local files in /var/lib/copr-rpmbuild/results INFO: --> SRPM url: file:///var/lib/copr-rpmbuild/results/zapzap-5.3.8-1.fc39.src.rpm INFO: Using review directory: /var/lib/copr-rpmbuild/results/zapzap WARNING: DNF4 command failed, retrying, attempt #2, sleeping 10s WARNING: No disttag found in prebuilt packages INFO: Use --define DISTTAG to set proper dist. e. g. --define DISTTAG fc21. ERROR: 'No disttag in package and no DISTTAG flag. Use --define DISTTAG to set proper dist e. g., --define DISTTAG=fc21.' (logs in /var/lib/copr-rpmbuild/results/cache/fedora-review.log) The build itself will not be marked as failed because of this Moving the results into `fedora-review' directory. Review template in: /var/lib/copr-rpmbuild/results/fedora-review/review.txt FedoraReview finished Running RPMResults tool Package info: { "packages": [ { "name": "zapzap", "epoch": null, "version": "5.3.8", "release": "1.fc39", "arch": "noarch" }, { "name": "zapzap", "epoch": null, "version": "5.3.8", "release": "1.fc39", "arch": "src" } ] } RPMResults finished