Thu May 9 23:29:14 UTC 2024 I: starting to build pyroma/trixie/arm64 on jenkins on '2024-05-09 23:28' Thu May 9 23:29:14 UTC 2024 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/arm64_13/17239/console.log Thu May 9 23:29:14 UTC 2024 I: Downloading source for trixie/pyroma=2.6b2-1 --2024-05-09 23:29:14-- http://deb.debian.org/debian/pool/main/p/pyroma/pyroma_2.6b2-1.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 1921 (1.9K) [text/prs.lines.tag] Saving to: ‘pyroma_2.6b2-1.dsc’ 0K . 100% 276M=0s 2024-05-09 23:29:14 (276 MB/s) - ‘pyroma_2.6b2-1.dsc’ saved [1921/1921] Thu May 9 23:29:14 UTC 2024 I: pyroma_2.6b2-1.dsc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: pyroma Binary: python3-pyroma Architecture: all Version: 2.6b2-1 Maintainer: Federico Ceratto Homepage: https://github.com/regebro/pyroma Standards-Version: 4.4.1 Vcs-Browser: https://salsa.debian.org/debian/pyroma Vcs-Git: https://salsa.debian.org/debian/pyroma.git Build-Depends: debhelper-compat (= 12) Build-Depends-Indep: dh-python, python3-all, python3-docutils, python3-pygments, python3-setuptools Package-List: python3-pyroma deb python optional arch=all Checksums-Sha1: b25a8cb3a9d8f9703aecfda67cf88bed4ea06f11 349252 pyroma_2.6b2.orig.tar.gz d9f3a178bbce621864533b81d8e5ef3c5ebd8000 2884 pyroma_2.6b2-1.debian.tar.xz Checksums-Sha256: 10b3851febfdde157e6155dbf2719f6ef656abb3d8b4075b3e4e6405ca79ac0c 349252 pyroma_2.6b2.orig.tar.gz 4b346a21a175939cfef52b26595db02f5e2989c641c8819f8b72fe16bf712179 2884 pyroma_2.6b2-1.debian.tar.xz Files: 8a310d91708aa38c1a1fb5792ccb0b82 349252 pyroma_2.6b2.orig.tar.gz 9b4c56eb5226d5384f46bcbaa93cbf57 2884 pyroma_2.6b2-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAl39/UcACgkQbzG8RPUX faq1PA//SS/wO4yyzENeJctZ+8qgG2IqguPTWnH7IIV9KNM0AJtFUc4hJdYPKzYY 4TOSEDrYL+BRauEYNssd99Qt3vc+sUyaeI2H4xNxiuCoRnnxHhvtInNy4kFy9Ri5 yREKKQbRymh81LiOK07seXJQM0dhHneN5Zdhfp4CFqMz79XisWatkVCUsavPpTTt T4Somb1AC08RK/9NuKrnBZkBY1EnT+trbgmZXjBgCTRpma+0MnFk6yUFxG5OJWgL FSU/n2/d8APJjVgQo77TjRteBb/AwFvs5zrekB7gEpbpqTNCm2itXVevqffzufXz nUuwwpzz/7CjAvmJexj6eCe9JJCzGTAzfeh9Y9EKNOxxC44RnpfeKeqA513FmX5E 6mZIEOvhjH8EeHiRrwafMesMqtnm+h1vsa0WmbaGnbO7aQ7FztyKrxQ1fFtc1B5X J7fk8Kn/LdILVQnn3iHk6fxulIc0/GSbl2ExdpMHHw3N9R/NZVnIVEyBMJMIDFLn C8QyukGurlcKmn62PSspHEJkNdLVGXqKp7nwqKpRe3Z8x1CUkP8eOrihoAErpsmD m9F3s/HV90ai1xJZD6L4kDIBlaUkX2hOaf5pAPF4uqHzYRO67mQK/fGZIYqrigpT 6UrQTsUvkSB6K0+1Yg8BW0xCzE68+jE4moW/ys+etGDQZJhnC4Y= =vv1V -----END PGP SIGNATURE----- Thu May 9 23:29:14 UTC 2024 I: Checking whether the package is not for us Thu May 9 23:29:14 UTC 2024 I: Starting 1st build on remote node codethink01-arm64.debian.net. Thu May 9 23:29:14 UTC 2024 I: Preparing to do remote build '1' on codethink01-arm64.debian.net. Thu May 9 23:30:01 UTC 2024 I: Deleting $TMPDIR on codethink01-arm64.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Wed Jun 11 17:52:16 -12 2025 I: pbuilder-time-stamp: 1749707536 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/trixie-reproducible-base.tgz] I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Copying source file I: copying [pyroma_2.6b2-1.dsc] I: copying [./pyroma_2.6b2.orig.tar.gz] I: copying [./pyroma_2.6b2-1.debian.tar.xz] I: Extracting source gpgv: Signature made Sat Dec 21 11:08:55 2019 gpgv: using RSA key 7CA7DDFB333921408C6F2B966F31BC44F5177DAA gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./pyroma_2.6b2-1.dsc: no acceptable signature found dpkg-source: info: extracting pyroma in pyroma-2.6b2 dpkg-source: info: unpacking pyroma_2.6b2.orig.tar.gz dpkg-source: info: unpacking pyroma_2.6b2-1.debian.tar.xz I: using fakeroot in build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/2011960/tmp/hooks/D02_print_environment starting I: set BUILDDIR='/build/reproducible-path' BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' BUILDUSERNAME='pbuilder1' BUILD_ARCH='arm64' DEBIAN_FRONTEND='noninteractive' DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' DISTRIBUTION='trixie' HOME='/root' HOST_ARCH='arm64' IFS=' ' INVOCATION_ID='cadc2d4a335e4848b6e022cce4d6088a' LANG='C' LANGUAGE='en_US:en' LC_ALL='C' MAIL='/var/mail/root' OPTIND='1' PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' PBCURRENTCOMMANDLINEOPERATION='build' PBUILDER_OPERATION='build' PBUILDER_PKGDATADIR='/usr/share/pbuilder' PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' PBUILDER_SYSCONFDIR='/etc' PPID='2011960' PS1='# ' PS2='> ' PS4='+ ' PWD='/' SHELL='/bin/bash' SHLVL='2' SUDO_COMMAND='/usr/bin/timeout -k 18.1h 18h /usr/bin/ionice -c 3 /usr/bin/nice /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/pbuilderrc_ADbs --distribution trixie --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/trixie-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/b1 --logfile b1/build.log pyroma_2.6b2-1.dsc' SUDO_GID='109' SUDO_UID='104' SUDO_USER='jenkins' TERM='unknown' TZ='/usr/share/zoneinfo/Etc/GMT+12' USER='root' _='/usr/bin/systemd-run' http_proxy='http://192.168.101.4:3128' I: uname -a Linux codethink01-arm64 6.1.0-21-cloud-arm64 #1 SMP Debian 6.1.90-1 (2024-05-03) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Jun 10 17:47 /bin -> usr/bin I: user script /srv/workspace/pbuilder/2011960/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: arm64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper-compat (= 12), dh-python, python3-all, python3-docutils, python3-pygments, python3-setuptools dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 19744 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on debhelper-compat (= 12); however: Package debhelper-compat is not installed. pbuilder-satisfydepends-dummy depends on dh-python; however: Package dh-python is not installed. pbuilder-satisfydepends-dummy depends on python3-all; however: Package python3-all is not installed. pbuilder-satisfydepends-dummy depends on python3-docutils; however: Package python3-docutils is not installed. pbuilder-satisfydepends-dummy depends on python3-pygments; however: Package python3-pygments is not installed. pbuilder-satisfydepends-dummy depends on python3-setuptools; however: Package python3-setuptools is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: autoconf{a} automake{a} autopoint{a} autotools-dev{a} bsdextrautils{a} debhelper{a} dh-autoreconf{a} dh-python{a} dh-strip-nondeterminism{a} docutils-common{a} dwz{a} file{a} gettext{a} gettext-base{a} groff-base{a} intltool-debian{a} libarchive-zip-perl{a} libdebhelper-perl{a} libelf1t64{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libicu72{a} libmagic-mgc{a} libmagic1t64{a} libpipeline1{a} libpython3-stdlib{a} libpython3.11-minimal{a} libpython3.11-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libreadline8t64{a} libsub-override-perl{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} po-debconf{a} python3{a} python3-all{a} python3-distutils{a} python3-docutils{a} python3-lib2to3{a} python3-minimal{a} python3-pkg-resources{a} python3-pygments{a} python3-roman{a} python3-setuptools{a} python3.11{a} python3.11-minimal{a} python3.12{a} python3.12-minimal{a} readline-common{a} sensible-utils{a} sgml-base{a} tzdata{a} xml-core{a} The following packages are RECOMMENDED but will NOT be installed: ca-certificates curl libarchive-cpio-perl libltdl-dev libmail-sendmail-perl libpaper-utils lynx python3-pil wget 0 packages upgraded, 59 newly installed, 0 to remove and 0 not upgraded. Need to get 32.0 MB of archives. After unpacking 138 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian trixie/main arm64 libpython3.11-minimal arm64 3.11.9-1 [813 kB] Get: 2 http://deb.debian.org/debian trixie/main arm64 libexpat1 arm64 2.6.2-1 [88.7 kB] Get: 3 http://deb.debian.org/debian trixie/main arm64 python3.11-minimal arm64 3.11.9-1 [1767 kB] Get: 4 http://deb.debian.org/debian trixie/main arm64 python3-minimal arm64 3.11.8-1 [26.3 kB] Get: 5 http://deb.debian.org/debian trixie/main arm64 media-types all 10.1.0 [26.9 kB] Get: 6 http://deb.debian.org/debian trixie/main arm64 netbase all 6.4 [12.8 kB] Get: 7 http://deb.debian.org/debian trixie/main arm64 tzdata all 2024a-4 [255 kB] Get: 8 http://deb.debian.org/debian trixie/main arm64 readline-common all 8.2-4 [69.3 kB] Get: 9 http://deb.debian.org/debian trixie/main arm64 libreadline8t64 arm64 8.2-4 [157 kB] Get: 10 http://deb.debian.org/debian trixie/main arm64 libpython3.11-stdlib arm64 3.11.9-1 [1775 kB] Get: 11 http://deb.debian.org/debian trixie/main arm64 python3.11 arm64 3.11.9-1 [602 kB] Get: 12 http://deb.debian.org/debian trixie/main arm64 libpython3-stdlib arm64 3.11.8-1 [9332 B] Get: 13 http://deb.debian.org/debian trixie/main arm64 python3 arm64 3.11.8-1 [27.4 kB] Get: 14 http://deb.debian.org/debian trixie/main arm64 libpython3.12-minimal arm64 3.12.3-1 [802 kB] Get: 15 http://deb.debian.org/debian trixie/main arm64 python3.12-minimal arm64 3.12.3-1 [1931 kB] Get: 16 http://deb.debian.org/debian trixie/main arm64 sgml-base all 1.31 [15.4 kB] Get: 17 http://deb.debian.org/debian trixie/main arm64 sensible-utils all 0.0.22 [22.4 kB] Get: 18 http://deb.debian.org/debian trixie/main arm64 libmagic-mgc arm64 1:5.45-3 [314 kB] Get: 19 http://deb.debian.org/debian trixie/main arm64 libmagic1t64 arm64 1:5.45-3 [100 kB] Get: 20 http://deb.debian.org/debian trixie/main arm64 file arm64 1:5.45-3 [43.0 kB] Get: 21 http://deb.debian.org/debian trixie/main arm64 gettext-base arm64 0.21-14+b1 [160 kB] Get: 22 http://deb.debian.org/debian trixie/main arm64 libuchardet0 arm64 0.0.8-1+b1 [69.0 kB] Get: 23 http://deb.debian.org/debian trixie/main arm64 groff-base arm64 1.23.0-4 [1130 kB] Get: 24 http://deb.debian.org/debian trixie/main arm64 bsdextrautils arm64 2.40-8 [93.0 kB] Get: 25 http://deb.debian.org/debian trixie/main arm64 libpipeline1 arm64 1.5.7-2 [36.5 kB] Get: 26 http://deb.debian.org/debian trixie/main arm64 man-db arm64 2.12.1-1 [1394 kB] Get: 27 http://deb.debian.org/debian trixie/main arm64 m4 arm64 1.4.19-4 [277 kB] Get: 28 http://deb.debian.org/debian trixie/main arm64 autoconf all 2.71-3 [332 kB] Get: 29 http://deb.debian.org/debian trixie/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 30 http://deb.debian.org/debian trixie/main arm64 automake all 1:1.16.5-1.3 [823 kB] Get: 31 http://deb.debian.org/debian trixie/main arm64 autopoint all 0.21-14 [496 kB] Get: 32 http://deb.debian.org/debian trixie/main arm64 libdebhelper-perl all 13.15.3 [88.0 kB] Get: 33 http://deb.debian.org/debian trixie/main arm64 libtool all 2.4.7-7 [517 kB] Get: 34 http://deb.debian.org/debian trixie/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 35 http://deb.debian.org/debian trixie/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 36 http://deb.debian.org/debian trixie/main arm64 libsub-override-perl all 0.10-1 [10.6 kB] Get: 37 http://deb.debian.org/debian trixie/main arm64 libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB] Get: 38 http://deb.debian.org/debian trixie/main arm64 dh-strip-nondeterminism all 1.13.1-1 [8620 B] Get: 39 http://deb.debian.org/debian trixie/main arm64 libelf1t64 arm64 0.191-1+b1 [187 kB] Get: 40 http://deb.debian.org/debian trixie/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 41 http://deb.debian.org/debian trixie/main arm64 libicu72 arm64 72.1-4+b1 [9224 kB] Get: 42 http://deb.debian.org/debian trixie/main arm64 libxml2 arm64 2.9.14+dfsg-1.3+b3 [624 kB] Get: 43 http://deb.debian.org/debian trixie/main arm64 gettext arm64 0.21-14+b1 [1249 kB] Get: 44 http://deb.debian.org/debian trixie/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 45 http://deb.debian.org/debian trixie/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 46 http://deb.debian.org/debian trixie/main arm64 debhelper all 13.15.3 [901 kB] Get: 47 http://deb.debian.org/debian trixie/main arm64 python3-pkg-resources all 68.1.2-2 [241 kB] Get: 48 http://deb.debian.org/debian trixie/main arm64 python3-lib2to3 all 3.12.3-1 [77.6 kB] Get: 49 http://deb.debian.org/debian trixie/main arm64 python3-distutils all 3.12.3-1 [131 kB] Get: 50 http://deb.debian.org/debian trixie/main arm64 python3-setuptools all 68.1.2-2 [468 kB] Get: 51 http://deb.debian.org/debian trixie/main arm64 dh-python all 6.20240422 [107 kB] Get: 52 http://deb.debian.org/debian trixie/main arm64 xml-core all 0.19 [20.1 kB] Get: 53 http://deb.debian.org/debian trixie/main arm64 docutils-common all 0.20.1+dfsg-3 [128 kB] Get: 54 http://deb.debian.org/debian trixie/main arm64 libpython3.12-stdlib arm64 3.12.3-1 [1889 kB] Get: 55 http://deb.debian.org/debian trixie/main arm64 python3.12 arm64 3.12.3-1 [659 kB] Get: 56 http://deb.debian.org/debian trixie/main arm64 python3-all arm64 3.11.8-1 [1056 B] Get: 57 http://deb.debian.org/debian trixie/main arm64 python3-roman all 3.3-3 [9880 B] Get: 58 http://deb.debian.org/debian trixie/main arm64 python3-docutils all 0.20.1+dfsg-3 [389 kB] Get: 59 http://deb.debian.org/debian trixie/main arm64 python3-pygments all 2.17.2+dfsg-1 [818 kB] Fetched 32.0 MB in 0s (157 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libpython3.11-minimal:arm64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 19744 files and directories currently installed.) Preparing to unpack .../libpython3.11-minimal_3.11.9-1_arm64.deb ... Unpacking libpython3.11-minimal:arm64 (3.11.9-1) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.2-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.2-1) ... Selecting previously unselected package python3.11-minimal. Preparing to unpack .../python3.11-minimal_3.11.9-1_arm64.deb ... Unpacking python3.11-minimal (3.11.9-1) ... Setting up libpython3.11-minimal:arm64 (3.11.9-1) ... Setting up libexpat1:arm64 (2.6.2-1) ... Setting up python3.11-minimal (3.11.9-1) ... Selecting previously unselected package python3-minimal. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 20060 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.11.8-1_arm64.deb ... Unpacking python3-minimal (3.11.8-1) ... Selecting previously unselected package media-types. Preparing to unpack .../1-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../2-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package tzdata. Preparing to unpack .../3-tzdata_2024a-4_all.deb ... Unpacking tzdata (2024a-4) ... Selecting previously unselected package readline-common. Preparing to unpack .../4-readline-common_8.2-4_all.deb ... Unpacking readline-common (8.2-4) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../5-libreadline8t64_8.2-4_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8 to /lib/aarch64-linux-gnu/libhistory.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8.2 to /lib/aarch64-linux-gnu/libhistory.so.8.2.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8 to /lib/aarch64-linux-gnu/libreadline.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8.2 to /lib/aarch64-linux-gnu/libreadline.so.8.2.usr-is-merged by libreadline8t64' Unpacking libreadline8t64:arm64 (8.2-4) ... Selecting previously unselected package libpython3.11-stdlib:arm64. Preparing to unpack .../6-libpython3.11-stdlib_3.11.9-1_arm64.deb ... Unpacking libpython3.11-stdlib:arm64 (3.11.9-1) ... Selecting previously unselected package python3.11. Preparing to unpack .../7-python3.11_3.11.9-1_arm64.deb ... Unpacking python3.11 (3.11.9-1) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../8-libpython3-stdlib_3.11.8-1_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.11.8-1) ... Setting up python3-minimal (3.11.8-1) ... Selecting previously unselected package python3. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 21052 files and directories currently installed.) Preparing to unpack .../00-python3_3.11.8-1_arm64.deb ... Unpacking python3 (3.11.8-1) ... Selecting previously unselected package libpython3.12-minimal:arm64. Preparing to unpack .../01-libpython3.12-minimal_3.12.3-1_arm64.deb ... Unpacking libpython3.12-minimal:arm64 (3.12.3-1) ... Selecting previously unselected package python3.12-minimal. Preparing to unpack .../02-python3.12-minimal_3.12.3-1_arm64.deb ... Unpacking python3.12-minimal (3.12.3-1) ... Selecting previously unselected package sgml-base. Preparing to unpack .../03-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../04-sensible-utils_0.0.22_all.deb ... Unpacking sensible-utils (0.0.22) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../05-libmagic-mgc_1%3a5.45-3_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../06-libmagic1t64_1%3a5.45-3_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3) ... Selecting previously unselected package file. Preparing to unpack .../07-file_1%3a5.45-3_arm64.deb ... Unpacking file (1:5.45-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../08-gettext-base_0.21-14+b1_arm64.deb ... Unpacking gettext-base (0.21-14+b1) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../09-libuchardet0_0.0.8-1+b1_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b1) ... Selecting previously unselected package groff-base. Preparing to unpack .../10-groff-base_1.23.0-4_arm64.deb ... Unpacking groff-base (1.23.0-4) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../11-bsdextrautils_2.40-8_arm64.deb ... Unpacking bsdextrautils (2.40-8) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../12-libpipeline1_1.5.7-2_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.7-2) ... Selecting previously unselected package man-db. Preparing to unpack .../13-man-db_2.12.1-1_arm64.deb ... Unpacking man-db (2.12.1-1) ... Selecting previously unselected package m4. Preparing to unpack .../14-m4_1.4.19-4_arm64.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../15-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../16-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../17-automake_1%3a1.16.5-1.3_all.deb ... Unpacking automake (1:1.16.5-1.3) ... Selecting previously unselected package autopoint. Preparing to unpack .../18-autopoint_0.21-14_all.deb ... Unpacking autopoint (0.21-14) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../19-libdebhelper-perl_13.15.3_all.deb ... Unpacking libdebhelper-perl (13.15.3) ... Selecting previously unselected package libtool. Preparing to unpack .../20-libtool_2.4.7-7_all.deb ... Unpacking libtool (2.4.7-7) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../21-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../22-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libsub-override-perl. Preparing to unpack .../23-libsub-override-perl_0.10-1_all.deb ... Unpacking libsub-override-perl (0.10-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../24-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../25-dh-strip-nondeterminism_1.13.1-1_all.deb ... Unpacking dh-strip-nondeterminism (1.13.1-1) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../26-libelf1t64_0.191-1+b1_arm64.deb ... Unpacking libelf1t64:arm64 (0.191-1+b1) ... Selecting previously unselected package dwz. Preparing to unpack .../27-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../28-libicu72_72.1-4+b1_arm64.deb ... Unpacking libicu72:arm64 (72.1-4+b1) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../29-libxml2_2.9.14+dfsg-1.3+b3_arm64.deb ... Unpacking libxml2:arm64 (2.9.14+dfsg-1.3+b3) ... Selecting previously unselected package gettext. Preparing to unpack .../30-gettext_0.21-14+b1_arm64.deb ... Unpacking gettext (0.21-14+b1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../31-intltool-debian_0.35.0+20060710.6_all.deb ... Unpacking intltool-debian (0.35.0+20060710.6) ... Selecting previously unselected package po-debconf. Preparing to unpack .../32-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../33-debhelper_13.15.3_all.deb ... Unpacking debhelper (13.15.3) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../34-python3-pkg-resources_68.1.2-2_all.deb ... Unpacking python3-pkg-resources (68.1.2-2) ... Selecting previously unselected package python3-lib2to3. Preparing to unpack .../35-python3-lib2to3_3.12.3-1_all.deb ... Unpacking python3-lib2to3 (3.12.3-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../36-python3-distutils_3.12.3-1_all.deb ... Unpacking python3-distutils (3.12.3-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../37-python3-setuptools_68.1.2-2_all.deb ... Unpacking python3-setuptools (68.1.2-2) ... Selecting previously unselected package dh-python. Preparing to unpack .../38-dh-python_6.20240422_all.deb ... Unpacking dh-python (6.20240422) ... Selecting previously unselected package xml-core. Preparing to unpack .../39-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../40-docutils-common_0.20.1+dfsg-3_all.deb ... Unpacking docutils-common (0.20.1+dfsg-3) ... Selecting previously unselected package libpython3.12-stdlib:arm64. Preparing to unpack .../41-libpython3.12-stdlib_3.12.3-1_arm64.deb ... Unpacking libpython3.12-stdlib:arm64 (3.12.3-1) ... Selecting previously unselected package python3.12. Preparing to unpack .../42-python3.12_3.12.3-1_arm64.deb ... Unpacking python3.12 (3.12.3-1) ... Selecting previously unselected package python3-all. Preparing to unpack .../43-python3-all_3.11.8-1_arm64.deb ... Unpacking python3-all (3.11.8-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../44-python3-roman_3.3-3_all.deb ... Unpacking python3-roman (3.3-3) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../45-python3-docutils_0.20.1+dfsg-3_all.deb ... Unpacking python3-docutils (0.20.1+dfsg-3) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../46-python3-pygments_2.17.2+dfsg-1_all.deb ... Unpacking python3-pygments (2.17.2+dfsg-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.7-2) ... Setting up libicu72:arm64 (72.1-4+b1) ... Setting up bsdextrautils (2.40-8) ... Setting up libmagic-mgc (1:5.45-3) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.15.3) ... Setting up libmagic1t64:arm64 (1:5.45-3) ... Setting up libpython3.12-minimal:arm64 (3.12.3-1) ... Setting up gettext-base (0.21-14+b1) ... Setting up m4 (1.4.19-4) ... Setting up file (1:5.45-3) ... Setting up libelf1t64:arm64 (0.191-1+b1) ... Setting up tzdata (2024a-4) ... Current default time zone: 'Etc/UTC' Local time is now: Thu Jun 12 05:52:33 UTC 2025. Universal Time is now: Thu Jun 12 05:52:33 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.21-14) ... Setting up autoconf (2.71-3) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.22) ... Setting up libuchardet0:arm64 (0.0.8-1+b1) ... Setting up libsub-override-perl (0.10-1) ... Setting up netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up readline-common (8.2-4) ... Setting up libxml2:arm64 (2.9.14+dfsg-1.3+b3) ... Setting up automake (1:1.16.5-1.3) ... update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode Setting up libfile-stripnondeterminism-perl (1.13.1-1) ... Setting up python3.12-minimal (3.12.3-1) ... Setting up gettext (0.21-14+b1) ... Setting up libtool (2.4.7-7) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up libreadline8t64:arm64 (8.2-4) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up groff-base (1.23.0-4) ... Setting up xml-core (0.19) ... Setting up libpython3.12-stdlib:arm64 (3.12.3-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up libpython3.11-stdlib:arm64 (3.11.9-1) ... Setting up python3.12 (3.12.3-1) ... Setting up man-db (2.12.1-1) ... Not building database; man-db/auto-update is not 'true'. Setting up libpython3-stdlib:arm64 (3.11.8-1) ... Setting up python3.11 (3.11.9-1) ... Setting up debhelper (13.15.3) ... Setting up python3 (3.11.8-1) ... Setting up python3-roman (3.3-3) ... Setting up python3-lib2to3 (3.12.3-1) ... Setting up python3-pkg-resources (68.1.2-2) ... Setting up python3-distutils (3.12.3-1) ... python3.12: can't get files for byte-compilation Setting up python3-setuptools (68.1.2-2) ... Setting up python3-all (3.11.8-1) ... Setting up python3-pygments (2.17.2+dfsg-1) ... Setting up dh-python (6.20240422) ... Processing triggers for libc-bin (2.38-7) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.20.1+dfsg-3) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.20.1+dfsg-3) ... Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Writing extended state information... Building tag database... -> Finished parsing the build-deps Reading package lists... Building dependency tree... Reading state information... fakeroot is already the newest version (1.33-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Building the package I: Running cd /build/reproducible-path/pyroma-2.6b2/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-genchanges -S > ../pyroma_2.6b2-1_source.changes dpkg-buildpackage: info: source package pyroma dpkg-buildpackage: info: source version 2.6b2-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Federico Ceratto dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 fakeroot debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild pybuild --clean -i python{version} -p "3.12 3.11" I: pybuild base:311: python3.12 setup.py clean running clean removing '/build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it I: pybuild base:311: python3.11 setup.py clean running clean removing '/build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.11' does not exist -- can't clean it rm -rf .pybuild/ find . -name \*.pyc -exec rm {} \; dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild rm -f debian/debhelper-build-stamp rm -rf debian/.debhelper/ rm -f -- debian/python3-pyroma.substvars debian/files rm -fr -- debian/python3-pyroma/ debian/tmp/ find . \( \( \ \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -type f -a \ \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \ -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \ -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \ -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \ \) -exec rm -f {} + \) -o \ \( -type d -a \( -name autom4te.cache -o -name __pycache__ \) -prune -exec rm -rf {} + \) \) debian/rules build dh build --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild pybuild --configure -i python{version} -p "3.12 3.11" I: pybuild base:311: python3.12 setup.py config running config I: pybuild base:311: python3.11 setup.py config running config dh_auto_build -O--buildsystem=pybuild pybuild --build -i python{version} -p "3.12 3.11" I: pybuild base:311: /usr/bin/python3.12 setup.py build running build running build_py creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/tests.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/ratings.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/pypidata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/projectdata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/distributiondata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/classifiers.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma copying pyroma/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma running egg_info creating pyroma.egg-info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt writing manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.distributions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.distributions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.distributions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.distributions' to be distributed and are already explicitly excluding 'pyroma.testdata.distributions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.distribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.distribute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.distribute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.distribute' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.distribute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete copying pyroma/testdata/complete/README.txt -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete copying pyroma/testdata/complete/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete copying pyroma/testdata/complete/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/tests.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/complete creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test/minimal copying pyroma/testdata/custom_test/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test/minimal creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.zip -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking/lacking copying pyroma/testdata/lacking/lacking/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking/lacking creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal/minimal copying pyroma/testdata/minimal/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal/minimal creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config copying pyroma/testdata/only_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config copying pyroma/testdata/only_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config/only_config copying pyroma/testdata/only_config/only_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config/only_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config/setup_config copying pyroma/testdata/setup_config/setup_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config/setup_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/completedata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/distributedata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/complete copying pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/complete creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/distribute copying pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/distribute I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/tests.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/ratings.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/pypidata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/projectdata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/distributiondata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/classifiers.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma copying pyroma/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.distributions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.distributions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.distributions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.distributions' to be distributed and are already explicitly excluding 'pyroma.testdata.distributions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.distribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.distribute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.distribute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.distribute' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.distribute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete copying pyroma/testdata/complete/README.txt -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete copying pyroma/testdata/complete/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete copying pyroma/testdata/complete/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/tests.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/complete creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test/minimal copying pyroma/testdata/custom_test/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test/minimal creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.zip -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions copying pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking/lacking copying pyroma/testdata/lacking/lacking/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking/lacking creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal/minimal copying pyroma/testdata/minimal/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal/minimal creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config copying pyroma/testdata/only_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config copying pyroma/testdata/only_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config/only_config copying pyroma/testdata/only_config/only_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config/only_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config/setup_config copying pyroma/testdata/setup_config/setup_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config/setup_config creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/completedata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/distributedata.py -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/complete copying pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/complete creating /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/distribute copying pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/distribute dh_auto_test -O--buildsystem=pybuild pybuild --test -i python{version} -p "3.12 3.11" I: pybuild base:311: python3.12 setup.py test running test WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. /usr/lib/python3/dist-packages/setuptools/command/test.py:193: _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`. ******************************************************************************** !! ir_d = dist.fetch_build_eggs(dist.install_requires) WARNING: The wheel package is not available. /usr/lib/python3/dist-packages/setuptools/command/test.py:194: _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`. ******************************************************************************** !! tr_d = dist.fetch_build_eggs(dist.tests_require or []) WARNING: The wheel package is not available. /usr/lib/python3/dist-packages/setuptools/command/test.py:195: _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`. ******************************************************************************** !! er_d = dist.fetch_build_eggs( WARNING: The wheel package is not available. running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' running build_ext test_complete (pyroma.tests.DistroDataTest.test_complete) ... /usr/lib/python3/dist-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. /usr/lib/python3.12/tarfile.py:2221: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. warnings.warn( WARNING: The wheel package is not available. WARNING: The wheel package is not available. /build/reproducible-path/pyroma-2.6b2/pyroma/distributiondata.py:22: ResourceWarning: unclosed file <_io.BufferedReader name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/distributions/complete-1.0.dev1.tar'> tarfile.open(name=path, mode="r:*").extractall(tempdir) ResourceWarning: Enable tracemalloc to get the object allocation traceback WARNING: The wheel package is not available. ok test_complete (pyroma.tests.ProjectDataTest.test_complete) ... WARNING: The wheel package is not available. ok test_complete (pyroma.tests.PyPITest.test_complete) ... /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:96: ResourceWarning: unclosed file <_io.TextIOWrapper name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/xmlrpcdata/completedata.py' mode='rt' encoding='UTF-8'> exec(open(filename, "rt").read(), None, data) ResourceWarning: Enable tracemalloc to get the object allocation traceback /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:57: ResourceWarning: unclosed file <_io.BufferedReader name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz'> return open(self.filename, "rb").read() ResourceWarning: Enable tracemalloc to get the object allocation traceback WARNING: The wheel package is not available. ok test_distribute (pyroma.tests.PyPITest.test_distribute) ... /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:96: ResourceWarning: unclosed file <_io.TextIOWrapper name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/xmlrpcdata/distributedata.py' mode='rt' encoding='UTF-8'> exec(open(filename, "rt").read(), None, data) ResourceWarning: Enable tracemalloc to get the object allocation traceback /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:57: ResourceWarning: unclosed file <_io.BufferedReader name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/distributions/distribute-0.6.15.tar.gz'> return open(self.filename, "rb").read() ResourceWarning: Enable tracemalloc to get the object allocation traceback /usr/lib/python3.12/tarfile.py:2221: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. warnings.warn( :13: ResourceWarning: unclosed file <_io.TextIOWrapper name='MANIFEST.in' mode='r' encoding='UTF-8'> ResourceWarning: Enable tracemalloc to get the object allocation traceback creating build creating build/src creating build/src/docs creating build/src/docs/_templates creating build/src/docs/_theme creating build/src/docs/_theme/nature creating build/src/docs/_theme/nature/static creating build/src/setuptools creating build/src/setuptools/command creating build/src/setuptools/tests creating build/src/setuptools/tests/indexes creating build/src/setuptools/tests/indexes/test_links_priority creating build/src/setuptools/tests/indexes/test_links_priority/simple creating build/src/setuptools/tests/indexes/test_links_priority/simple/foobar creating build/src/tests creating build/src/tests/shlib_test copying setuptools/archive_util.py -> build/src/setuptools copying setuptools/__init__.py -> build/src/setuptools copying setuptools/sandbox.py -> build/src/setuptools copying setuptools/dist.py -> build/src/setuptools copying setuptools/package_index.py -> build/src/setuptools copying setuptools/depends.py -> build/src/setuptools copying setuptools/extension.py -> build/src/setuptools copying setuptools/command/install.py -> build/src/setuptools/command copying setuptools/command/build_py.py -> build/src/setuptools/command copying setuptools/command/upload_docs.py -> build/src/setuptools/command copying setuptools/command/develop.py -> build/src/setuptools/command copying setuptools/command/install_egg_info.py -> build/src/setuptools/command copying setuptools/command/__init__.py -> build/src/setuptools/command copying setuptools/command/build_ext.py -> build/src/setuptools/command copying setuptools/command/bdist_rpm.py -> build/src/setuptools/command copying setuptools/command/test.py -> build/src/setuptools/command copying setuptools/command/register.py -> build/src/setuptools/command copying setuptools/command/upload.py -> build/src/setuptools/command copying setuptools/command/bdist_egg.py -> build/src/setuptools/command copying setuptools/command/install_lib.py -> build/src/setuptools/command copying setuptools/command/egg_info.py -> build/src/setuptools/command copying setuptools/command/easy_install.py -> build/src/setuptools/command copying setuptools/command/setopt.py -> build/src/setuptools/command copying setuptools/command/saveopts.py -> build/src/setuptools/command copying setuptools/command/bdist_wininst.py -> build/src/setuptools/command copying setuptools/command/sdist.py -> build/src/setuptools/command copying setuptools/command/install_scripts.py -> build/src/setuptools/command copying setuptools/command/alias.py -> build/src/setuptools/command copying setuptools/command/rotate.py -> build/src/setuptools/command copying setuptools/tests/test_upload_docs.py -> build/src/setuptools/tests copying setuptools/tests/__init__.py -> build/src/setuptools/tests copying setuptools/tests/test_develop.py -> build/src/setuptools/tests copying setuptools/tests/test_easy_install.py -> build/src/setuptools/tests copying setuptools/tests/test_build_ext.py -> build/src/setuptools/tests copying setuptools/tests/doctest.py -> build/src/setuptools/tests copying setuptools/tests/test_packageindex.py -> build/src/setuptools/tests copying setuptools/tests/server.py -> build/src/setuptools/tests copying setuptools/tests/test_sandbox.py -> build/src/setuptools/tests copying setuptools/tests/test_resources.py -> build/src/setuptools/tests copying setuptools/tests/win_script_wrapper.txt -> build/src/setuptools/tests copying setuptools/cli.exe -> build/src/setuptools copying setuptools/gui.exe -> build/src/setuptools copying tests/test_distribute_setup.py -> build/src/tests copying tests/manual_test.py -> build/src/tests copying tests/install_test.py -> build/src/tests copying tests/shlib_test/setup.py -> build/src/tests/shlib_test copying tests/shlib_test/test_hello.py -> build/src/tests/shlib_test copying tests/shlib_test/hello.c -> build/src/tests/shlib_test copying tests/shlib_test/hellolib.c -> build/src/tests/shlib_test copying tests/shlib_test/hello.pyx -> build/src/tests/shlib_test copying tests/api_tests.txt -> build/src/tests :24: DeprecationWarning: lib2to3 package is deprecated and may not be able to parse Python 3.10+ Generating grammar tables from /usr/lib/python3.12/lib2to3/Grammar.txt Generating grammar tables from /usr/lib/python3.12/lib2to3/PatternGrammar.txt Skipping optional fixer: buffer Skipping optional fixer: idioms Skipping optional fixer: set_literal Skipping optional fixer: ws_comma Refactored build/src/tests/api_tests.txt --- build/src/tests/api_tests.txt (original) +++ build/src/tests/api_tests.txt (refactored) @@ -39,7 +39,7 @@ >>> dist.py_version == sys.version[:3] True - >>> print dist.platform + >>> print(dist.platform) None Including various computed attributes:: @@ -199,7 +199,7 @@ You can ask a WorkingSet to ``find()`` a distribution matching a requirement:: >>> from pkg_resources import Requirement - >>> print ws.find(Requirement.parse("Foo==1.0")) # no match, return None + >>> print(ws.find(Requirement.parse("Foo==1.0"))) # no match, return None None >>> ws.find(Requirement.parse("Bar==0.9")) # match, return distribution @@ -211,7 +211,7 @@ >>> try: ... ws.find(Requirement.parse("Bar==1.0")) ... except VersionConflict: - ... print 'ok' + ... print('ok') ok You can subscribe a callback function to receive notifications whenever a new @@ -219,7 +219,7 @@ once for each existing distribution in the working set, and then is called again for new distributions added thereafter:: - >>> def added(dist): print "Added", dist + >>> def added(dist): print("Added", dist) >>> ws.subscribe(added) Added Bar 0.9 >>> foo12 = Distribution(project_name="Foo", version="1.2", location="f12") Files that were modified: build/src/tests/api_tests.txt copying setuptools/tests/indexes/test_links_priority/external.html -> build/src/setuptools/tests/indexes/test_links_priority copying setuptools/tests/indexes/test_links_priority/simple/foobar/index.html -> build/src/setuptools/tests/indexes/test_links_priority/simple/foobar copying docs/conf.py -> build/src/docs copying docs/setuptools.txt -> build/src/docs copying docs/easy_install.txt -> build/src/docs copying docs/python3.txt -> build/src/docs copying docs/using.txt -> build/src/docs copying docs/index.txt -> build/src/docs copying docs/pkg_resources.txt -> build/src/docs copying docs/roadmap.txt -> build/src/docs copying docs/_theme/nature/theme.conf -> build/src/docs/_theme/nature copying docs/_theme/nature/static/pygments.css -> build/src/docs/_theme/nature/static copying docs/_theme/nature/static/nature.css_t -> build/src/docs/_theme/nature/static copying docs/Makefile -> build/src/docs copying docs/_templates/indexsidebar.html -> build/src/docs/_templates copying pkg_resources.py -> build/src copying distribute_setup.py -> build/src copying site.py -> build/src copying easy_install.py -> build/src copying setup.py -> build/src copying CHANGES.txt -> build/src copying DEVGUIDE.txt -> build/src copying CONTRIBUTORS.txt -> build/src copying README.txt -> build/src copying MANIFEST.in -> build/src copying launcher.c -> build/src /build/reproducible-path/pyroma-2.6b2/pyroma/projectdata.py:131: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead logging.warn("Exception when running setup.", exc_info=True) Exception when running setup. Traceback (most recent call last): File "/build/reproducible-path/pyroma-2.6b2/pyroma/projectdata.py", line 124, in run_setup exec(f.read(), glocals, glocals) File "", line 27, in AttributeError: module 'distutils.util' has no attribute 'run_2to3' ok test_complete (pyroma.tests.RatingsTest.test_complete) ... /usr/lib/python3/dist-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. ok test_custom_test (pyroma.tests.RatingsTest.test_custom_test) ... /usr/lib/python3/dist-packages/setuptools/dist.py:509: SetuptoolsDeprecationWarning: Invalid version: '0.0foo'. !! ******************************************************************************** The version specified is not a valid version according to PEP 440. This may not work as expected with newer versions of setuptools, pip, and PyPI. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://peps.python.org/pep-0440/ for details. ******************************************************************************** !! self._validate_version(self.metadata.version) ok test_lacking (pyroma.tests.RatingsTest.test_lacking) ... ok test_markdown (pyroma.tests.RatingsTest.test_markdown) ... ok test_minimal (pyroma.tests.RatingsTest.test_minimal) ... /usr/lib/python3/dist-packages/setuptools/dist.py:509: SetuptoolsDeprecationWarning: Invalid version: '0.0foo'. !! ******************************************************************************** The version specified is not a valid version according to PEP 440. This may not work as expected with newer versions of setuptools, pip, and PyPI. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://peps.python.org/pep-0440/ for details. ******************************************************************************** !! self._validate_version(self.metadata.version) ok test_only_config (pyroma.tests.RatingsTest.test_only_config) ... /build/reproducible-path/pyroma-2.6b2/pyroma/projectdata.py:179: SetuptoolsDeprecationWarning: Deprecated API usage. !! ******************************************************************************** As setuptools moves its configuration towards `pyproject.toml`, `setuptools.config.read_configuration` became deprecated. For the time being, you can use the `setuptools.config.setupcfg` module to access a backward compatible API, but this module is provisional and might be removed in the future. To read project metadata, consider using ``build.util.project_wheel_metadata`` (https://pypi.org/project/build/). For simple scenarios, you can also try parsing the file directly with the help of ``configparser``. ******************************************************************************** !! data = config.read_configuration("setup.cfg") ok test_setup_config (pyroma.tests.RatingsTest.test_setup_config) ... ok ---------------------------------------------------------------------- Ran 11 tests in 0.482s OK I: pybuild base:311: python3.11 setup.py test running test WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. /usr/lib/python3/dist-packages/setuptools/command/test.py:193: _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`. ******************************************************************************** !! ir_d = dist.fetch_build_eggs(dist.install_requires) WARNING: The wheel package is not available. /usr/lib/python3/dist-packages/setuptools/command/test.py:194: _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`. ******************************************************************************** !! tr_d = dist.fetch_build_eggs(dist.tests_require or []) WARNING: The wheel package is not available. /usr/lib/python3/dist-packages/setuptools/command/test.py:195: _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`. ******************************************************************************** !! er_d = dist.fetch_build_eggs( WARNING: The wheel package is not available. running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' running build_ext test_complete (pyroma.tests.DistroDataTest.test_complete) ... /usr/lib/python3/dist-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. WARNING: The wheel package is not available. WARNING: The wheel package is not available. /build/reproducible-path/pyroma-2.6b2/pyroma/distributiondata.py:22: ResourceWarning: unclosed file <_io.BufferedReader name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/distributions/complete-1.0.dev1.tar'> tarfile.open(name=path, mode="r:*").extractall(tempdir) ResourceWarning: Enable tracemalloc to get the object allocation traceback WARNING: The wheel package is not available. ok test_complete (pyroma.tests.ProjectDataTest.test_complete) ... WARNING: The wheel package is not available. ok test_complete (pyroma.tests.PyPITest.test_complete) ... /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:96: ResourceWarning: unclosed file <_io.TextIOWrapper name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/xmlrpcdata/completedata.py' mode='rt' encoding='UTF-8'> exec(open(filename, "rt").read(), None, data) ResourceWarning: Enable tracemalloc to get the object allocation traceback /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:57: ResourceWarning: unclosed file <_io.BufferedReader name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz'> return open(self.filename, "rb").read() ResourceWarning: Enable tracemalloc to get the object allocation traceback WARNING: The wheel package is not available. ok test_distribute (pyroma.tests.PyPITest.test_distribute) ... /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:96: ResourceWarning: unclosed file <_io.TextIOWrapper name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/xmlrpcdata/distributedata.py' mode='rt' encoding='UTF-8'> exec(open(filename, "rt").read(), None, data) ResourceWarning: Enable tracemalloc to get the object allocation traceback /build/reproducible-path/pyroma-2.6b2/pyroma/tests.py:57: ResourceWarning: unclosed file <_io.BufferedReader name='/build/reproducible-path/pyroma-2.6b2/pyroma/testdata/distributions/distribute-0.6.15.tar.gz'> return open(self.filename, "rb").read() ResourceWarning: Enable tracemalloc to get the object allocation traceback :13: ResourceWarning: unclosed file <_io.TextIOWrapper name='MANIFEST.in' mode='r' encoding='UTF-8'> ResourceWarning: Enable tracemalloc to get the object allocation traceback creating build creating build/src creating build/src/docs creating build/src/docs/_templates creating build/src/docs/_theme creating build/src/docs/_theme/nature creating build/src/docs/_theme/nature/static creating build/src/setuptools creating build/src/setuptools/command creating build/src/setuptools/tests creating build/src/setuptools/tests/indexes creating build/src/setuptools/tests/indexes/test_links_priority creating build/src/setuptools/tests/indexes/test_links_priority/simple creating build/src/setuptools/tests/indexes/test_links_priority/simple/foobar creating build/src/tests creating build/src/tests/shlib_test copying setuptools/archive_util.py -> build/src/setuptools copying setuptools/__init__.py -> build/src/setuptools copying setuptools/sandbox.py -> build/src/setuptools copying setuptools/dist.py -> build/src/setuptools copying setuptools/package_index.py -> build/src/setuptools copying setuptools/depends.py -> build/src/setuptools copying setuptools/extension.py -> build/src/setuptools copying setuptools/command/install.py -> build/src/setuptools/command copying setuptools/command/build_py.py -> build/src/setuptools/command copying setuptools/command/upload_docs.py -> build/src/setuptools/command copying setuptools/command/develop.py -> build/src/setuptools/command copying setuptools/command/install_egg_info.py -> build/src/setuptools/command copying setuptools/command/__init__.py -> build/src/setuptools/command copying setuptools/command/build_ext.py -> build/src/setuptools/command copying setuptools/command/bdist_rpm.py -> build/src/setuptools/command copying setuptools/command/test.py -> build/src/setuptools/command copying setuptools/command/register.py -> build/src/setuptools/command copying setuptools/command/upload.py -> build/src/setuptools/command copying setuptools/command/bdist_egg.py -> build/src/setuptools/command copying setuptools/command/install_lib.py -> build/src/setuptools/command copying setuptools/command/egg_info.py -> build/src/setuptools/command copying setuptools/command/easy_install.py -> build/src/setuptools/command copying setuptools/command/setopt.py -> build/src/setuptools/command copying setuptools/command/saveopts.py -> build/src/setuptools/command copying setuptools/command/bdist_wininst.py -> build/src/setuptools/command copying setuptools/command/sdist.py -> build/src/setuptools/command copying setuptools/command/install_scripts.py -> build/src/setuptools/command copying setuptools/command/alias.py -> build/src/setuptools/command copying setuptools/command/rotate.py -> build/src/setuptools/command copying setuptools/tests/test_upload_docs.py -> build/src/setuptools/tests copying setuptools/tests/__init__.py -> build/src/setuptools/tests copying setuptools/tests/test_develop.py -> build/src/setuptools/tests copying setuptools/tests/test_easy_install.py -> build/src/setuptools/tests copying setuptools/tests/test_build_ext.py -> build/src/setuptools/tests copying setuptools/tests/doctest.py -> build/src/setuptools/tests copying setuptools/tests/test_packageindex.py -> build/src/setuptools/tests copying setuptools/tests/server.py -> build/src/setuptools/tests copying setuptools/tests/test_sandbox.py -> build/src/setuptools/tests copying setuptools/tests/test_resources.py -> build/src/setuptools/tests copying setuptools/tests/win_script_wrapper.txt -> build/src/setuptools/tests copying setuptools/cli.exe -> build/src/setuptools copying setuptools/gui.exe -> build/src/setuptools copying tests/test_distribute_setup.py -> build/src/tests copying tests/manual_test.py -> build/src/tests copying tests/install_test.py -> build/src/tests copying tests/shlib_test/setup.py -> build/src/tests/shlib_test copying tests/shlib_test/test_hello.py -> build/src/tests/shlib_test copying tests/shlib_test/hello.c -> build/src/tests/shlib_test copying tests/shlib_test/hellolib.c -> build/src/tests/shlib_test copying tests/shlib_test/hello.pyx -> build/src/tests/shlib_test copying tests/api_tests.txt -> build/src/tests :24: DeprecationWarning: lib2to3 package is deprecated and may not be able to parse Python 3.10+ Generating grammar tables from /usr/lib/python3.11/lib2to3/Grammar.txt Generating grammar tables from /usr/lib/python3.11/lib2to3/PatternGrammar.txt Skipping optional fixer: buffer Skipping optional fixer: idioms Skipping optional fixer: set_literal Skipping optional fixer: ws_comma Refactored build/src/tests/api_tests.txt --- build/src/tests/api_tests.txt (original) +++ build/src/tests/api_tests.txt (refactored) @@ -39,7 +39,7 @@ >>> dist.py_version == sys.version[:3] True - >>> print dist.platform + >>> print(dist.platform) None Including various computed attributes:: @@ -199,7 +199,7 @@ You can ask a WorkingSet to ``find()`` a distribution matching a requirement:: >>> from pkg_resources import Requirement - >>> print ws.find(Requirement.parse("Foo==1.0")) # no match, return None + >>> print(ws.find(Requirement.parse("Foo==1.0"))) # no match, return None None >>> ws.find(Requirement.parse("Bar==0.9")) # match, return distribution @@ -211,7 +211,7 @@ >>> try: ... ws.find(Requirement.parse("Bar==1.0")) ... except VersionConflict: - ... print 'ok' + ... print('ok') ok You can subscribe a callback function to receive notifications whenever a new @@ -219,7 +219,7 @@ once for each existing distribution in the working set, and then is called again for new distributions added thereafter:: - >>> def added(dist): print "Added", dist + >>> def added(dist): print("Added", dist) >>> ws.subscribe(added) Added Bar 0.9 >>> foo12 = Distribution(project_name="Foo", version="1.2", location="f12") Files that were modified: build/src/tests/api_tests.txt copying setuptools/tests/indexes/test_links_priority/external.html -> build/src/setuptools/tests/indexes/test_links_priority copying setuptools/tests/indexes/test_links_priority/simple/foobar/index.html -> build/src/setuptools/tests/indexes/test_links_priority/simple/foobar copying docs/conf.py -> build/src/docs copying docs/setuptools.txt -> build/src/docs copying docs/easy_install.txt -> build/src/docs copying docs/python3.txt -> build/src/docs copying docs/using.txt -> build/src/docs copying docs/index.txt -> build/src/docs copying docs/pkg_resources.txt -> build/src/docs copying docs/roadmap.txt -> build/src/docs copying docs/_theme/nature/theme.conf -> build/src/docs/_theme/nature copying docs/_theme/nature/static/pygments.css -> build/src/docs/_theme/nature/static copying docs/_theme/nature/static/nature.css_t -> build/src/docs/_theme/nature/static copying docs/Makefile -> build/src/docs copying docs/_templates/indexsidebar.html -> build/src/docs/_templates copying pkg_resources.py -> build/src copying distribute_setup.py -> build/src copying site.py -> build/src copying easy_install.py -> build/src copying setup.py -> build/src copying CHANGES.txt -> build/src copying DEVGUIDE.txt -> build/src copying CONTRIBUTORS.txt -> build/src copying README.txt -> build/src copying MANIFEST.in -> build/src copying launcher.c -> build/src /build/reproducible-path/pyroma-2.6b2/pyroma/projectdata.py:131: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead logging.warn("Exception when running setup.", exc_info=True) Exception when running setup. Traceback (most recent call last): File "/build/reproducible-path/pyroma-2.6b2/pyroma/projectdata.py", line 124, in run_setup exec(f.read(), glocals, glocals) File "", line 27, in AttributeError: module 'distutils.util' has no attribute 'run_2to3' ok test_complete (pyroma.tests.RatingsTest.test_complete) ... /usr/lib/python3/dist-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. ok test_custom_test (pyroma.tests.RatingsTest.test_custom_test) ... /usr/lib/python3/dist-packages/setuptools/dist.py:509: SetuptoolsDeprecationWarning: Invalid version: '0.0foo'. !! ******************************************************************************** The version specified is not a valid version according to PEP 440. This may not work as expected with newer versions of setuptools, pip, and PyPI. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://peps.python.org/pep-0440/ for details. ******************************************************************************** !! self._validate_version(self.metadata.version) ok test_lacking (pyroma.tests.RatingsTest.test_lacking) ... ok test_markdown (pyroma.tests.RatingsTest.test_markdown) ... ok test_minimal (pyroma.tests.RatingsTest.test_minimal) ... /usr/lib/python3/dist-packages/setuptools/dist.py:509: SetuptoolsDeprecationWarning: Invalid version: '0.0foo'. !! ******************************************************************************** The version specified is not a valid version according to PEP 440. This may not work as expected with newer versions of setuptools, pip, and PyPI. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://peps.python.org/pep-0440/ for details. ******************************************************************************** !! self._validate_version(self.metadata.version) ok test_only_config (pyroma.tests.RatingsTest.test_only_config) ... /build/reproducible-path/pyroma-2.6b2/pyroma/projectdata.py:179: SetuptoolsDeprecationWarning: Deprecated API usage. !! ******************************************************************************** As setuptools moves its configuration towards `pyproject.toml`, `setuptools.config.read_configuration` became deprecated. For the time being, you can use the `setuptools.config.setupcfg` module to access a backward compatible API, but this module is provisional and might be removed in the future. To read project metadata, consider using ``build.util.project_wheel_metadata`` (https://pypi.org/project/build/). For simple scenarios, you can also try parsing the file directly with the help of ``configparser``. ******************************************************************************** !! data = config.read_configuration("setup.cfg") ok test_setup_config (pyroma.tests.RatingsTest.test_setup_config) ... ok ---------------------------------------------------------------------- Ran 11 tests in 0.519s OK create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild rm -f -- debian/python3-pyroma.substvars rm -fr -- debian/.debhelper/generated/python3-pyroma/ debian/python3-pyroma/ debian/tmp/ debian/rules override_dh_auto_install make[1]: Entering directory '/build/reproducible-path/pyroma-2.6b2' dh_auto_install install -m0755 -d /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma pybuild --install -i python{version} -p "3.12 3.11" --dest-dir /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma I: pybuild base:311: /usr/bin/python3.12 setup.py install --root /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.distributions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.distributions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.distributions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.distributions' to be distributed and are already explicitly excluding 'pyroma.testdata.distributions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.distribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.distribute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.distribute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.distribute' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.distribute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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 /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12 creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata/distribute copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata/distribute creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/distributedata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/xmlrpcdata/completedata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config/setup_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/setup_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/only_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/only_config/only_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config/only_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/only_config/only_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/only_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/only_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/only_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/minimal/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking/lacking copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking/lacking/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking/lacking copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/lacking/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.zip -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.tar -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/distributions creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/custom_test/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/complete/tests.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/complete/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/testdata/complete/README.txt -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/classifiers.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/distributiondata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/projectdata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/pypidata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/ratings.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.12_pyroma/build/pyroma/tests.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata/distributedata.py to distributedata.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/xmlrpcdata/completedata.py to completedata.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config/setup_config/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/setup_config/setup.py to setup.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/only_config/only_config/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal/minimal/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/minimal/setup.py to setup.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking/lacking/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/lacking/setup.py to setup.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test/minimal/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/custom_test/setup.py to setup.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete/complete/tests.py to tests.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete/complete/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/testdata/complete/setup.py to setup.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/classifiers.py to classifiers.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/distributiondata.py to distributiondata.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/projectdata.py to projectdata.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/pypidata.py to pypidata.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/ratings.py to ratings.cpython-312.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma/tests.py to tests.cpython-312.pyc running install_egg_info Copying pyroma.egg-info to /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.12/dist-packages/pyroma-2.6b2.egg-info Skipping SOURCES.txt running install_scripts Installing pyroma script to /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/bin I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.complete.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.complete.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.complete.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.custom_test.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.custom_test.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.custom_test.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.distributions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.distributions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.distributions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.distributions' to be distributed and are already explicitly excluding 'pyroma.testdata.distributions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.lacking.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking.lacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.lacking.lacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.lacking.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking.lacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.minimal.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal.minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.minimal.minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.minimal.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal.minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.only_config.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config.only_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.only_config.only_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.only_config.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config.only_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.setup_config.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config.setup_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.setup_config.setup_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.setup_config.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config.setup_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.complete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.complete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.complete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pyroma.testdata.xmlrpcdata.distribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.distribute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pyroma.testdata.xmlrpcdata.distribute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pyroma.testdata.xmlrpcdata.distribute' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.distribute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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 /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11 creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata/distribute copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata/distribute creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/distributedata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/xmlrpcdata/completedata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config/setup_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/setup_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/only_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/only_config/only_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config/only_config/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/only_config/only_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/only_config copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/only_config/README.txt -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/only_config creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/minimal/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking/lacking copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking/lacking/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking/lacking copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/lacking/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.zip -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/distributions copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/distributions/complete-1.0.dev1.tar -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/distributions creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test/minimal/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test/minimal copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/custom_test/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete creating /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/complete/tests.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/complete/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/setup.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/setup.cfg -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/testdata/complete/README.txt -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/__init__.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/classifiers.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/distributiondata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/projectdata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/pypidata.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/ratings.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma copying /build/reproducible-path/pyroma-2.6b2/.pybuild/cpython3_3.11_pyroma/build/pyroma/tests.py -> /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata/distributedata.py to distributedata.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/xmlrpcdata/completedata.py to completedata.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config/setup_config/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/setup_config/setup.py to setup.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/only_config/only_config/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal/minimal/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/minimal/setup.py to setup.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking/lacking/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/lacking/setup.py to setup.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test/minimal/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/custom_test/setup.py to setup.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete/complete/tests.py to tests.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete/complete/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/testdata/complete/setup.py to setup.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/classifiers.py to classifiers.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/distributiondata.py to distributiondata.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/projectdata.py to projectdata.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/pypidata.py to pypidata.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/ratings.py to ratings.cpython-311.pyc byte-compiling /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma/tests.py to tests.cpython-311.pyc running install_egg_info Copying pyroma.egg-info to /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/lib/python3.11/dist-packages/pyroma-2.6b2.egg-info Skipping SOURCES.txt running install_scripts Installing pyroma script to /build/reproducible-path/pyroma-2.6b2/debian/python3-pyroma/usr/bin # Renaming Python3 binary mv debian/python3-pyroma/usr/bin/pyroma debian/python3-pyroma/usr/bin/pyroma3 make[1]: Leaving directory '/build/reproducible-path/pyroma-2.6b2' dh_installdocs -O--buildsystem=pybuild install -m0755 -d debian/python3-pyroma/usr/share/doc/python3-pyroma install -m0755 -d debian/python3-pyroma/usr/share/doc/python3-pyroma cp --reflink=auto -a ./DEVELOPMENT.rst debian/python3-pyroma/usr/share/doc/python3-pyroma cp --reflink=auto -a ./README.rst debian/python3-pyroma/usr/share/doc/python3-pyroma chown -R 0:0 debian/python3-pyroma/usr/share/doc chmod -R u\+rw,go=rX debian/python3-pyroma/usr/share/doc install -p -m0644 debian/copyright debian/python3-pyroma/usr/share/doc/python3-pyroma/copyright rm -f debian/python3-pyroma.debhelper.log debian/rules override_dh_installchangelogs make[1]: Entering directory '/build/reproducible-path/pyroma-2.6b2' dh_installchangelogs HISTORY.txt install -m0755 -d debian/python3-pyroma/usr/share/doc/python3-pyroma install -p -m0644 debian/.debhelper/generated/python3-pyroma/dh_installchangelogs.dch.trimmed debian/python3-pyroma/usr/share/doc/python3-pyroma/changelog.Debian install -p -m0644 HISTORY.txt debian/python3-pyroma/usr/share/doc/python3-pyroma/changelog make[1]: Leaving directory '/build/reproducible-path/pyroma-2.6b2' dh_installman -O--buildsystem=pybuild install -m0755 -d debian/python3-pyroma/usr/share/man/man1/ install -p -m0644 ./debian/pyroma3.1 debian/python3-pyroma/usr/share/man/man1/pyroma3.1 man-recode --to-code UTF-8 --suffix .dh-new debian/python3-pyroma/usr/share/man/man1/pyroma3.1 mv debian/python3-pyroma/usr/share/man/man1/pyroma3.1.dh-new debian/python3-pyroma/usr/share/man/man1/pyroma3.1 chmod 0644 -- debian/python3-pyroma/usr/share/man/man1/pyroma3.1 dh_python3 -O--buildsystem=pybuild D: dh_python3 dh_python3:179: version: 6.20240422 D: dh_python3 dh_python3:180: argv: ['/usr/bin/dh_python3', '-O--buildsystem=pybuild'] D: dh_python3 dh_python3:181: options: Namespace(guess_deps=True, skip_private=False, verbose=True, arch=None, package=None, no_package=None, remaining_packages=False, compile_all=False, vrange=None, regexpr=None, accept_upstream_versions=False, depends=None, depends_section=None, recommends=None, recommends_section=None, suggests=None, suggests_section=None, requires=None, shebang=None, ignore_shebangs=False, clean_dbg_pkg=True, no_ext_rename=False, no_shebang_rewrite=False, private_dir=None, O=['--buildsystem=pybuild']) D: dh_python3 dh_python3:182: supported Python versions: 3.11,3.12 (default=3.11) D: dh_python3 debhelper:174: source=pyroma, binary packages=['python3-pyroma'] D: dh_python3 dh_python3:204: processing package python3-pyroma... D: dh_python3 fs:50: moving files from debian/python3-pyroma/usr/lib/python3.11/dist-packages to debian/python3-pyroma/usr/lib/python3/dist-packages/ D: dh_python3 fs:50: moving files from debian/python3-pyroma/usr/lib/python3.12/dist-packages to debian/python3-pyroma/usr/lib/python3/dist-packages/ D: dh_python3 fs:335: package python3-pyroma details = {'requires.txt': {'debian/python3-pyroma/usr/lib/python3/dist-packages/pyroma-2.6b2.egg-info/requires.txt'}, 'egg-info': {'debian/python3-pyroma/usr/lib/python3/dist-packages/pyroma-2.6b2.egg-info/PKG-INFO'}, 'dist-info': set(), 'nsp.txt': set(), 'shebangs': {/usr/bin/python3}, 'public_vers': {Version('3')}, 'private_dirs': {}, 'compile': True, 'ext_vers': set(), 'ext_no_version': set()} D: dh_python3 depends:103: generating dependencies for package python3-pyroma D: dh_python3 pydist:173: trying to find dependency for docutils (python=None) D: dh_python3 pydist:207: dependency: module seems to be installed D: dh_python3 pydist:270: dependency: included in build-deps D: dh_python3 pydist:173: trying to find dependency for pygments (python=None) D: dh_python3 pydist:207: dependency: module seems to be installed D: dh_python3 pydist:270: dependency: included in build-deps D: dh_python3 pydist:173: trying to find dependency for setuptools (python=None) D: dh_python3 pydist:207: dependency: module seems to be installed D: dh_python3 pydist:270: dependency: included in build-deps D: dh_python3 depends:253: D={'python3-pygments', 'python3-docutils', 'python3-pkg-resources', 'python3:any'}; R=[]; S=[]; E=[], B=[]; RT=[] dh_installinit -O--buildsystem=pybuild dh_installsystemduser -O--buildsystem=pybuild dh_lintian -O--buildsystem=pybuild install -m0755 -d debian/python3-pyroma/usr/share/lintian/overrides install -p -m0644 debian/python3-pyroma.lintian-overrides debian/python3-pyroma/usr/share/lintian/overrides/python3-pyroma dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild Using 1576923915 as canonical time Normalizing debian/python3-pyroma/usr/lib/python3/dist-packages/pyroma/testdata/distributions/distribute-0.6.15.tar.gz using File::StripNondeterminism::handlers::gzip Normalizing debian/python3-pyroma/usr/lib/python3/dist-packages/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz using File::StripNondeterminism::handlers::gzip Normalizing debian/python3-pyroma/usr/lib/python3/dist-packages/pyroma/testdata/distributions/complete-1.0.dev1.zip using File::StripNondeterminism::handlers::zip dh_compress -O--buildsystem=pybuild cd debian/python3-pyroma chmod a-x usr/share/doc/python3-pyroma/changelog usr/share/doc/python3-pyroma/changelog.Debian usr/share/man/man1/pyroma3.1 gzip -9nf usr/share/doc/python3-pyroma/changelog usr/share/doc/python3-pyroma/changelog.Debian usr/share/man/man1/pyroma3.1 cd '/build/reproducible-path/pyroma-2.6b2' dh_fixperms -O--buildsystem=pybuild find debian/python3-pyroma -true -print0 2>/dev/null | xargs -0r chown --no-dereference 0:0 find debian/python3-pyroma ! -type l -a -true -a -true -print0 2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s find debian/python3-pyroma/usr/share/doc -type f -a -true -a ! -regex 'debian/python3-pyroma/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null | xargs -0r chmod 0644 find debian/python3-pyroma/usr/share/doc -type d -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0755 find debian/python3-pyroma/usr/share/man debian/python3-pyroma/usr/share/lintian/overrides -type f -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0644 find debian/python3-pyroma -type f \( -name '*.so.*' -o -name '*.so' -o -name '*.la' -o -name '*.a' -o -name '*.js' -o -name '*.css' -o -name '*.scss' -o -name '*.sass' -o -name '*.jpeg' -o -name '*.jpg' -o -name '*.png' -o -name '*.gif' -o -name '*.cmxs' -o -name '*.node' \) -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0644 find debian/python3-pyroma/usr/bin -type f -a -true -a -true -print0 2>/dev/null | xargs -0r chmod a+x find debian/python3-pyroma/usr/lib -type f -name '*.ali' -a -true -a -true -print0 2>/dev/null | xargs -0r chmod uga-w dh_missing -O--buildsystem=pybuild dh_installdeb -O--buildsystem=pybuild install -m0755 -d debian/python3-pyroma/DEBIAN printf '#!/bin/sh\nset -e\n' > debian/python3-pyroma/DEBIAN/postinst cat debian/python3-pyroma.postinst.debhelper >> debian/python3-pyroma/DEBIAN/postinst chmod 0755 -- debian/python3-pyroma/DEBIAN/postinst chown 0:0 -- debian/python3-pyroma/DEBIAN/postinst printf '#!/bin/sh\nset -e\n' > debian/python3-pyroma/DEBIAN/prerm cat debian/python3-pyroma.prerm.debhelper >> debian/python3-pyroma/DEBIAN/prerm chmod 0755 -- debian/python3-pyroma/DEBIAN/prerm chown 0:0 -- debian/python3-pyroma/DEBIAN/prerm dh_gencontrol -O--buildsystem=pybuild install -m0755 -d debian/python3-pyroma/DEBIAN echo misc:Depends= >> debian/python3-pyroma.substvars echo misc:Pre-Depends= >> debian/python3-pyroma.substvars dpkg-gencontrol -ppython3-pyroma -ldebian/changelog -Tdebian/python3-pyroma.substvars -cdebian/control -Pdebian/python3-pyroma dpkg-gencontrol: warning: Recommends field of package python3-pyroma: substitution variable ${python3:Recommends} used, but is not defined dpkg-gencontrol: warning: Provides field of package python3-pyroma: substitution variable ${python3:Provides} used, but is not defined chmod 0644 -- debian/python3-pyroma/DEBIAN/control chown 0:0 -- debian/python3-pyroma/DEBIAN/control dh_md5sums -O--buildsystem=pybuild install -m0755 -d debian/python3-pyroma/DEBIAN cd debian/python3-pyroma >/dev/null && xargs -r0 md5sum | perl -pe 'if (s@^\\@@) { s/\\\\/\\/g; }' > DEBIAN/md5sums chmod 0644 -- debian/python3-pyroma/DEBIAN/md5sums chown 0:0 -- debian/python3-pyroma/DEBIAN/md5sums dh_builddeb -O--buildsystem=pybuild dpkg-deb --build debian/python3-pyroma .. dpkg-deb: building package 'python3-pyroma' in '../python3-pyroma_2.6b2-1_all.deb'. dpkg-genbuildinfo --build=binary -O../pyroma_2.6b2-1_arm64.buildinfo dpkg-genchanges --build=binary -O../pyroma_2.6b2-1_arm64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /srv/workspace/pbuilder/2011960 and its subdirectories I: Current time: Wed Jun 11 17:52:59 -12 2025 I: pbuilder-time-stamp: 1749707579 Thu May 9 23:30:02 UTC 2024 I: 1st build successful. Starting 2nd build on remote node codethink02-arm64.debian.net. Thu May 9 23:30:02 UTC 2024 I: Preparing to do remote build '2' on codethink02-arm64.debian.net. Thu May 9 23:30:49 UTC 2024 I: Deleting $TMPDIR on codethink02-arm64.debian.net. Thu May 9 23:30:50 UTC 2024 I: pyroma_2.6b2-1_arm64.changes: Format: 1.8 Date: Sat, 21 Dec 2019 10:25:15 +0000 Source: pyroma Binary: python3-pyroma Architecture: all Version: 2.6b2-1 Distribution: unstable Urgency: medium Maintainer: Federico Ceratto Changed-By: Federico Ceratto Description: python3-pyroma - Python packaging quality checker (Python3 build) Closes: 937527 Changes: pyroma (2.6b2-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field . [ Federico Ceratto ] * New upstream release * Drop Python 2 package (Closes: #937527) Checksums-Sha1: d8cb218540d0da45defce993c47224fc743cd13b 5767 pyroma_2.6b2-1_arm64.buildinfo 20f94dd731d239e1bdbe20ed2067a77b8cd567af 345620 python3-pyroma_2.6b2-1_all.deb Checksums-Sha256: 2c8025d641f402303f3654a3cf791f30866a56be391fcec1b36b8bb1c7381f61 5767 pyroma_2.6b2-1_arm64.buildinfo 49ff6a55da90798b10ede9656c2c11ee7cfa05ff60f1e6498d0a322ff8b0caa2 345620 python3-pyroma_2.6b2-1_all.deb Files: f902a15e7fb94be01bfb60345fd3db83 5767 python optional pyroma_2.6b2-1_arm64.buildinfo 7b6ce5c1d90421960556fe80f82b364c 345620 python optional python3-pyroma_2.6b2-1_all.deb Thu May 9 23:30:51 UTC 2024 I: diffoscope 265 will be used to compare the two builds: Running as unit: rb-diffoscope-arm64_13-17239.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/pyroma_2.6b2-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/pyroma_2.6b2-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/pyroma_2.6b2-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/b1/pyroma_2.6b2-1_arm64.changes /srv/reproducible-results/rbuild-debian/r-b-build.ZAIlCcNg/b2/pyroma_2.6b2-1_arm64.changes ## command (total time: 0.000s) 0.000s 1 call cmp (internal) ## has_same_content_as (total time: 0.000s) 0.000s 1 call abc.DotChangesFile ## main (total time: 0.363s) 0.363s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.018s) 0.018s 12 calls diffoscope.comparators.binary.FilesystemFile ## specialize (total time: 0.000s) 0.000s 1 call specialize Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 717ms CPU time consumed: 701ms Thu May 9 23:30:52 UTC 2024 I: diffoscope 265 found no differences in the changes files, and a .buildinfo file also exists. Thu May 9 23:30:52 UTC 2024 I: pyroma from trixie built successfully and reproducibly on arm64. Thu May 9 23:30:54 UTC 2024 I: Submitting .buildinfo files to external archives: Thu May 9 23:30:54 UTC 2024 I: Submitting 8.0K b1/pyroma_2.6b2-1_arm64.buildinfo.asc Thu May 9 23:30:55 UTC 2024 I: Submitting 8.0K b2/pyroma_2.6b2-1_arm64.buildinfo.asc Thu May 9 23:30:56 UTC 2024 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Thu May 9 23:30:56 UTC 2024 I: Done submitting .buildinfo files. Thu May 9 23:30:56 UTC 2024 I: Removing signed pyroma_2.6b2-1_arm64.buildinfo.asc files: removed './b1/pyroma_2.6b2-1_arm64.buildinfo.asc' removed './b2/pyroma_2.6b2-1_arm64.buildinfo.asc'