Running as unit: rb-build-arm64_11-85165.service ==================================================================================== Sat Feb 22 14:28:15 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_arm64_11) on jenkins, called using "codethink04-arm64 codethink03-arm64" as arguments. Sat Feb 22 14:28:15 UTC 2025 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-9g5H09sy" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Sat Feb 22 14:28:15 UTC 2025 - checking /var/lib/jenkins/offline_nodes if codethink04-arm64.debian.net is marked as down. Sat Feb 22 14:28:15 UTC 2025 - checking via ssh if codethink04-arm64.debian.net is up. removed '/tmp/read-only-fs-test-PN3LKd' Sat Feb 22 14:28:16 UTC 2025 - checking /var/lib/jenkins/offline_nodes if codethink03-arm64.debian.net is marked as down. Sat Feb 22 14:28:16 UTC 2025 - checking via ssh if codethink03-arm64.debian.net is up. removed '/tmp/read-only-fs-test-FRIUev' ok, let's check if python3-dmm is building anywhere yet… ok, python3-dmm is not building anywhere… UPDATE 1 ============================================================================= Initialising reproducibly build of python3-dmm in trixie on arm64 on jenkins now. 1st build will be done on codethink04-arm64.debian.net. 2nd build will be done on codethink03-arm64.debian.net. ============================================================================= Sat Feb 22 14:28:40 UTC 2025 I: starting to build python3-dmm/trixie/arm64 on jenkins on '2025-02-22 14:28' Sat Feb 22 14:28:40 UTC 2025 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/arm64_11/85165/console.log 1740234520 arm64 trixie python3-dmm Sat Feb 22 14:28:40 UTC 2025 I: Downloading source for trixie/python3-dmm=0.1.1-1 --2025-02-22 14:28:40-- http://deb.debian.org/debian/pool/main/p/python3-dmm/python3-dmm_0.1.1-1.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2027 (2.0K) [text/prs.lines.tag] Saving to: ‘python3-dmm_0.1.1-1.dsc’ 0K . 100% 246M=0s 2025-02-22 14:28:40 (246 MB/s) - ‘python3-dmm_0.1.1-1.dsc’ saved [2027/2027] --2025-02-22 14:28:40-- http://deb.debian.org/debian/pool/main/p/python3-dmm/python3-dmm_0.1.1-1.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2027 (2.0K) [text/prs.lines.tag] Saving to: ‘python3-dmm_0.1.1-1.dsc’ 0K . 100% 246M=0s 2025-02-22 14:28:40 (246 MB/s) - ‘python3-dmm_0.1.1-1.dsc’ saved [2027/2027] Sat Feb 22 14:28:40 UTC 2025 I: python3-dmm_0.1.1-1.dsc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: python3-dmm Binary: python3-dmm, dmm-utils Architecture: all Version: 0.1.1-1 Maintainer: Jonathan Carter Homepage: https://salsa.debian.org/jcc/distribution-management-modules Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/jcc/distribution-management-modules Vcs-Git: https://salsa.debian.org/jcc/distribution-management-modules.git Build-Depends: debhelper-compat (= 13), dh-python, python3-setuptools, python3 Package-List: dmm-utils deb python optional arch=all python3-dmm deb python optional arch=all Checksums-Sha1: 36242765d5b9038bbb26df2b02b9364773214050 227377 python3-dmm_0.1.1.orig.tar.gz 58fba0275175b942a4f50fcf47b1265b8097a015 2244 python3-dmm_0.1.1-1.debian.tar.xz Checksums-Sha256: 45b32405bb0e5e47955b6e8d4bf0b9a8135f4891382676a90311f049ef4ba6d2 227377 python3-dmm_0.1.1.orig.tar.gz f6531bdf70aa8a1e5f634179fdf7a8c90b51ab134e29c2dbe472cb60a07b0e20 2244 python3-dmm_0.1.1-1.debian.tar.xz Files: 96b257991d363496bff9eef5187e1d24 227377 python3-dmm_0.1.1.orig.tar.gz 3b21ff0af1fc4eea4ec274722e1359f9 2244 python3-dmm_0.1.1-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmPjT4IPHGpjY0BkZWJp YW4ub3JnAAoJELAdGnKsjcmhSbsQAM0AhQVi9Fe2O+8ljQeVaGkkkwfXhKGhjRdR qrHxcg5Euk1SMomWMJd7o1NtMAAafeXIap+B4zHKJUjz3GYH+BhEWcM0b/1/a3Ie k0+sYDEvcUQVV3zBA1ecC79o8i+v/9OEOeW84dr/ZXGHrYds/2ezcLbxPTc4yGhW JW8BQA6+PV0cEiUtdxxUe3Mku56/ER214D4cCla0S4OjxXFZX8a1CL3alr++uSZv Rm6kya0lbwmjGAncvzwhE4bbe8kPcoiUgbvI51T4WAj6KsqnXRUFOdGMFuQ4J1jN OLdR5lHDDSLcHY0MKe8JF88tI/dSptZW6Wsi9nt5yGLCzvrZqoBMbPukIAUlqnPA IUT2TL31ovFqfJKsyNaqbxCJgm5bkG3opA2HTs9ZDYeCSLIz+j8wIw2XFGX6muys Oz8k79a3aF4HGJIv+DOZEiYCFla/8UhuNTjs80+hLdp5yfDmCkPLiLxeexA1BEKf tzUxrRpxSSYjNr+9c5F8bIlEn51QBXaM6u4hjIq7KhvmPCqN8Wvz2JX3qrbvDv6T LE8L6RpviPsR520vFqLz0spgYtqvZc55fP4arObXgCvl6I277W/qJjnm6n6+W2FP 4XUw7gHpK+fhF+ucJR0jQTx1AAfsJ1LOZsXce2mzJ9Lh9mGsYXbClXWTO2Kgt2KU 1RVbl0XX =9Zjl -----END PGP SIGNATURE----- Sat Feb 22 14:28:40 UTC 2025 I: Checking whether the package is not for us Sat Feb 22 14:28:40 UTC 2025 I: Starting 1st build on remote node codethink04-arm64.debian.net. Sat Feb 22 14:28:40 UTC 2025 I: Preparing to do remote build '1' on codethink04-arm64.debian.net. Sat Feb 22 14:28:40 UTC 2025 - checking /var/lib/jenkins/offline_nodes if codethink04-arm64.debian.net is marked as down. Sat Feb 22 14:28:40 UTC 2025 - checking via ssh if codethink04-arm64.debian.net is up. removed '/tmp/read-only-fs-test-iT9FbU' ==================================================================================== Sat Feb 22 14:28:42 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job /srv/jenkins/bin/reproducible_build.sh) on codethink04-arm64, called using "1 python3-dmm trixie /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb 0.1.1-1" as arguments. Sat Feb 22 14:28:42 UTC 2025 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-0pBrM0Er" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Sat Feb 22 14:28:42 UTC 2025 I: Downloading source for trixie/python3-dmm=0.1.1-1 Reading package lists... NOTICE: 'python3-dmm' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/jcc/distribution-management-modules.git Please use: git clone https://salsa.debian.org/jcc/distribution-management-modules.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 232 kB of source archives. Get:1 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (dsc) [2027 B] Get:2 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (tar) [227 kB] Get:3 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (diff) [2244 B] Fetched 232 kB in 0s (2058 kB/s) Download complete and in download only mode Reading package lists... NOTICE: 'python3-dmm' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/jcc/distribution-management-modules.git Please use: git clone https://salsa.debian.org/jcc/distribution-management-modules.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 232 kB of source archives. Get:1 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (dsc) [2027 B] Get:2 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (tar) [227 kB] Get:3 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (diff) [2244 B] Fetched 232 kB in 0s (2058 kB/s) Download complete and in download only mode ============================================================================= Building python3-dmm in trixie on arm64 on codethink04-arm64 now. Date: Sat Feb 22 14:28:42 GMT 2025 Date UTC: Sat Feb 22 14:28:42 UTC 2025 ============================================================================= W: /root/.pbuilderrc does not exist I: Logging to b1/build.log I: pbuilder: network access will be disabled during build I: Current time: Sat Feb 22 02:28:42 -12 2025 I: pbuilder-time-stamp: 1740234522 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 [python3-dmm_0.1.1-1.dsc] I: copying [./python3-dmm_0.1.1.orig.tar.gz] I: copying [./python3-dmm_0.1.1-1.debian.tar.xz] I: Extracting source dpkg-source: warning: cannot verify inline signature for ./python3-dmm_0.1.1-1.dsc: unsupported subcommand dpkg-source: info: extracting python3-dmm in python3-dmm-0.1.1 dpkg-source: info: unpacking python3-dmm_0.1.1.orig.tar.gz dpkg-source: info: unpacking python3-dmm_0.1.1-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/3301095/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='b2363ea5bbf24a6dab6e738328e0bf29' 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='3301095' 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.yP0UuGAb/pbuilderrc_oxP6 --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.yP0UuGAb/b1 --logfile b1/build.log python3-dmm_0.1.1-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 codethink04-arm64 6.1.0-31-cloud-arm64 #1 SMP Debian 6.1.128-1 (2025-02-07) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Nov 22 14:40 /bin -> usr/bin I: user script /srv/workspace/pbuilder/3301095/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 (= 13), dh-python, python3-setuptools, python3 dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 19972 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 (= 13); 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-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3; however: Package python3 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} 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} libffi8{a} libfile-stripnondeterminism-perl{a} libicu72{a} libmagic-mgc{a} libmagic1t64{a} libpipeline1{a} libpython3-stdlib{a} libpython3.13-minimal{a} libpython3.13-stdlib{a} libreadline8t64{a} libtool{a} libuchardet0{a} libunistring5{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} po-debconf{a} python3{a} python3-autocommand{a} python3-inflect{a} python3-jaraco.context{a} python3-jaraco.functools{a} python3-jaraco.text{a} python3-minimal{a} python3-more-itertools{a} python3-pkg-resources{a} python3-setuptools{a} python3-typeguard{a} python3-typing-extensions{a} python3-zipp{a} python3.13{a} python3.13-minimal{a} readline-common{a} sensible-utils{a} tzdata{a} The following packages are RECOMMENDED but will NOT be installed: ca-certificates curl libarchive-cpio-perl libltdl-dev libmail-sendmail-perl lynx wget 0 packages upgraded, 56 newly installed, 0 to remove and 0 not upgraded. Need to get 27.6 MB of archives. After unpacking 114 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian trixie/main arm64 libpython3.13-minimal arm64 3.13.2-1 [853 kB] Get: 2 http://deb.debian.org/debian trixie/main arm64 libexpat1 arm64 2.6.4-1 [90.7 kB] Get: 3 http://deb.debian.org/debian trixie/main arm64 python3.13-minimal arm64 3.13.2-1 [1997 kB] Get: 4 http://deb.debian.org/debian trixie/main arm64 python3-minimal arm64 3.13.1-2 [27.0 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 2025a-2 [259 kB] Get: 8 http://deb.debian.org/debian trixie/main arm64 libffi8 arm64 3.4.7-1 [21.2 kB] Get: 9 http://deb.debian.org/debian trixie/main arm64 readline-common all 8.2-6 [69.4 kB] Get: 10 http://deb.debian.org/debian trixie/main arm64 libreadline8t64 arm64 8.2-6 [159 kB] Get: 11 http://deb.debian.org/debian trixie/main arm64 libpython3.13-stdlib arm64 3.13.2-1 [1914 kB] Get: 12 http://deb.debian.org/debian trixie/main arm64 python3.13 arm64 3.13.2-1 [745 kB] Get: 13 http://deb.debian.org/debian trixie/main arm64 libpython3-stdlib arm64 3.13.1-2 [9952 B] Get: 14 http://deb.debian.org/debian trixie/main arm64 python3 arm64 3.13.1-2 [28.0 kB] Get: 15 http://deb.debian.org/debian trixie/main arm64 sensible-utils all 0.0.24 [24.8 kB] Get: 16 http://deb.debian.org/debian trixie/main arm64 libmagic-mgc arm64 1:5.45-3+b1 [314 kB] Get: 17 http://deb.debian.org/debian trixie/main arm64 libmagic1t64 arm64 1:5.45-3+b1 [102 kB] Get: 18 http://deb.debian.org/debian trixie/main arm64 file arm64 1:5.45-3+b1 [43.4 kB] Get: 19 http://deb.debian.org/debian trixie/main arm64 gettext-base arm64 0.23.1-1 [241 kB] Get: 20 http://deb.debian.org/debian trixie/main arm64 libuchardet0 arm64 0.0.8-1+b2 [69.2 kB] Get: 21 http://deb.debian.org/debian trixie/main arm64 groff-base arm64 1.23.0-7 [1129 kB] Get: 22 http://deb.debian.org/debian trixie/main arm64 bsdextrautils arm64 2.40.4-3 [92.0 kB] Get: 23 http://deb.debian.org/debian trixie/main arm64 libpipeline1 arm64 1.5.8-1 [40.2 kB] Get: 24 http://deb.debian.org/debian trixie/main arm64 man-db arm64 2.13.0-1 [1404 kB] Get: 25 http://deb.debian.org/debian trixie/main arm64 m4 arm64 1.4.19-5 [284 kB] Get: 26 http://deb.debian.org/debian trixie/main arm64 autoconf all 2.72-3 [493 kB] Get: 27 http://deb.debian.org/debian trixie/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 28 http://deb.debian.org/debian trixie/main arm64 automake all 1:1.17-3 [862 kB] Get: 29 http://deb.debian.org/debian trixie/main arm64 autopoint all 0.23.1-1 [770 kB] Get: 30 http://deb.debian.org/debian trixie/main arm64 libdebhelper-perl all 13.24.1 [90.9 kB] Get: 31 http://deb.debian.org/debian trixie/main arm64 libtool all 2.5.4-3 [539 kB] Get: 32 http://deb.debian.org/debian trixie/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 33 http://deb.debian.org/debian trixie/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 34 http://deb.debian.org/debian trixie/main arm64 libfile-stripnondeterminism-perl all 1.14.1-2 [19.7 kB] Get: 35 http://deb.debian.org/debian trixie/main arm64 dh-strip-nondeterminism all 1.14.1-2 [8620 B] Get: 36 http://deb.debian.org/debian trixie/main arm64 libelf1t64 arm64 0.192-4 [189 kB] Get: 37 http://deb.debian.org/debian trixie/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 38 http://deb.debian.org/debian trixie/main arm64 libunistring5 arm64 1.3-1 [449 kB] Get: 39 http://deb.debian.org/debian trixie/main arm64 libicu72 arm64 72.1-6 [9239 kB] Get: 40 http://deb.debian.org/debian trixie/main arm64 libxml2 arm64 2.12.7+dfsg+really2.9.14-0.2+b1 [630 kB] Get: 41 http://deb.debian.org/debian trixie/main arm64 gettext arm64 0.23.1-1 [1610 kB] Get: 42 http://deb.debian.org/debian trixie/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 43 http://deb.debian.org/debian trixie/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 44 http://deb.debian.org/debian trixie/main arm64 debhelper all 13.24.1 [920 kB] Get: 45 http://deb.debian.org/debian trixie/main arm64 python3-autocommand all 2.2.2-3 [13.6 kB] Get: 46 http://deb.debian.org/debian trixie/main arm64 python3-more-itertools all 10.6.0-1 [65.3 kB] Get: 47 http://deb.debian.org/debian trixie/main arm64 python3-typing-extensions all 4.12.2-2 [73.0 kB] Get: 48 http://deb.debian.org/debian trixie/main arm64 python3-typeguard all 4.4.1-1 [37.0 kB] Get: 49 http://deb.debian.org/debian trixie/main arm64 python3-inflect all 7.3.1-2 [32.4 kB] Get: 50 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.context all 6.0.0-1 [7984 B] Get: 51 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.functools all 4.1.0-1 [12.0 kB] Get: 52 http://deb.debian.org/debian trixie/main arm64 python3-pkg-resources all 75.6.0-1 [222 kB] Get: 53 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.text all 4.0.0-1 [11.4 kB] Get: 54 http://deb.debian.org/debian trixie/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 55 http://deb.debian.org/debian trixie/main arm64 python3-setuptools all 75.6.0-1 [720 kB] Get: 56 http://deb.debian.org/debian trixie/main arm64 dh-python all 6.20250108 [113 kB] Fetched 27.6 MB in 0s (151 MB/s) Preconfiguring packages ... Selecting previously unselected package libpython3.13-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 ... 19972 files and directories currently installed.) Preparing to unpack .../libpython3.13-minimal_3.13.2-1_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.2-1) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.4-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.4-1) ... Selecting previously unselected package python3.13-minimal. Preparing to unpack .../python3.13-minimal_3.13.2-1_arm64.deb ... Unpacking python3.13-minimal (3.13.2-1) ... Setting up libpython3.13-minimal:arm64 (3.13.2-1) ... Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.13-minimal (3.13.2-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 ... 20306 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.13.1-2_arm64.deb ... Unpacking python3-minimal (3.13.1-2) ... 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_2025a-2_all.deb ... Unpacking tzdata (2025a-2) ... Selecting previously unselected package libffi8:arm64. Preparing to unpack .../4-libffi8_3.4.7-1_arm64.deb ... Unpacking libffi8:arm64 (3.4.7-1) ... Selecting previously unselected package readline-common. Preparing to unpack .../5-readline-common_8.2-6_all.deb ... Unpacking readline-common (8.2-6) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../6-libreadline8t64_8.2-6_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-6) ... Selecting previously unselected package libpython3.13-stdlib:arm64. Preparing to unpack .../7-libpython3.13-stdlib_3.13.2-1_arm64.deb ... Unpacking libpython3.13-stdlib:arm64 (3.13.2-1) ... Selecting previously unselected package python3.13. Preparing to unpack .../8-python3.13_3.13.2-1_arm64.deb ... Unpacking python3.13 (3.13.2-1) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../9-libpython3-stdlib_3.13.1-2_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3-minimal (3.13.1-2) ... 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 ... 21316 files and directories currently installed.) Preparing to unpack .../00-python3_3.13.1-2_arm64.deb ... Unpacking python3 (3.13.1-2) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../01-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../02-libmagic-mgc_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3+b1) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../03-libmagic1t64_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3+b1) ... Selecting previously unselected package file. Preparing to unpack .../04-file_1%3a5.45-3+b1_arm64.deb ... Unpacking file (1:5.45-3+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../05-gettext-base_0.23.1-1_arm64.deb ... Unpacking gettext-base (0.23.1-1) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../06-libuchardet0_0.0.8-1+b2_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b2) ... Selecting previously unselected package groff-base. Preparing to unpack .../07-groff-base_1.23.0-7_arm64.deb ... Unpacking groff-base (1.23.0-7) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../08-bsdextrautils_2.40.4-3_arm64.deb ... Unpacking bsdextrautils (2.40.4-3) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../09-libpipeline1_1.5.8-1_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../10-man-db_2.13.0-1_arm64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../11-m4_1.4.19-5_arm64.deb ... Unpacking m4 (1.4.19-5) ... Selecting previously unselected package autoconf. Preparing to unpack .../12-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../13-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../14-automake_1%3a1.17-3_all.deb ... Unpacking automake (1:1.17-3) ... Selecting previously unselected package autopoint. Preparing to unpack .../15-autopoint_0.23.1-1_all.deb ... Unpacking autopoint (0.23.1-1) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../16-libdebhelper-perl_13.24.1_all.deb ... Unpacking libdebhelper-perl (13.24.1) ... Selecting previously unselected package libtool. Preparing to unpack .../17-libtool_2.5.4-3_all.deb ... Unpacking libtool (2.5.4-3) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../18-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../19-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../20-libfile-stripnondeterminism-perl_1.14.1-2_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.1-2) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../21-dh-strip-nondeterminism_1.14.1-2_all.deb ... Unpacking dh-strip-nondeterminism (1.14.1-2) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../22-libelf1t64_0.192-4_arm64.deb ... Unpacking libelf1t64:arm64 (0.192-4) ... Selecting previously unselected package dwz. Preparing to unpack .../23-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libunistring5:arm64. Preparing to unpack .../24-libunistring5_1.3-1_arm64.deb ... Unpacking libunistring5:arm64 (1.3-1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../25-libicu72_72.1-6_arm64.deb ... Unpacking libicu72:arm64 (72.1-6) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../26-libxml2_2.12.7+dfsg+really2.9.14-0.2+b1_arm64.deb ... Unpacking libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Selecting previously unselected package gettext. Preparing to unpack .../27-gettext_0.23.1-1_arm64.deb ... Unpacking gettext (0.23.1-1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../28-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 .../29-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../30-debhelper_13.24.1_all.deb ... Unpacking debhelper (13.24.1) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../31-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../32-python3-more-itertools_10.6.0-1_all.deb ... Unpacking python3-more-itertools (10.6.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../33-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../34-python3-typeguard_4.4.1-1_all.deb ... Unpacking python3-typeguard (4.4.1-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../35-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../36-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../37-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../38-python3-pkg-resources_75.6.0-1_all.deb ... Unpacking python3-pkg-resources (75.6.0-1) ... Selecting previously unselected package python3-jaraco.text. Preparing to unpack .../39-python3-jaraco.text_4.0.0-1_all.deb ... Unpacking python3-jaraco.text (4.0.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../40-python3-zipp_3.21.0-1_all.deb ... Unpacking python3-zipp (3.21.0-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../41-python3-setuptools_75.6.0-1_all.deb ... Unpacking python3-setuptools (75.6.0-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../42-dh-python_6.20250108_all.deb ... Unpacking dh-python (6.20250108) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.8-1) ... Setting up libicu72:arm64 (72.1-6) ... Setting up bsdextrautils (2.40.4-3) ... Setting up libmagic-mgc (1:5.45-3+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.24.1) ... Setting up libmagic1t64:arm64 (1:5.45-3+b1) ... Setting up gettext-base (0.23.1-1) ... Setting up m4 (1.4.19-5) ... Setting up file (1:5.45-3+b1) ... Setting up libelf1t64:arm64 (0.192-4) ... Setting up tzdata (2025a-2) ... Current default time zone: 'Etc/UTC' Local time is now: Sat Feb 22 14:29:03 UTC 2025. Universal Time is now: Sat Feb 22 14:29:03 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up libunistring5:arm64 (1.3-1) ... Setting up autopoint (0.23.1-1) ... Setting up autoconf (2.72-3) ... Setting up libffi8:arm64 (3.4.7-1) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libuchardet0:arm64 (0.0.8-1+b2) ... Setting up netbase (6.4) ... Setting up readline-common (8.2-6) ... Setting up libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Setting up automake (1:1.17-3) ... update-alternatives: using /usr/bin/automake-1.17 to provide /usr/bin/automake (automake) in auto mode Setting up libfile-stripnondeterminism-perl (1.14.1-2) ... Setting up gettext (0.23.1-1) ... Setting up libtool (2.5.4-3) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up libreadline8t64:arm64 (8.2-6) ... Setting up dh-strip-nondeterminism (1.14.1-2) ... Setting up groff-base (1.23.0-7) ... Setting up libpython3.13-stdlib:arm64 (3.13.2-1) ... Setting up libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3.13 (3.13.2-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up python3 (3.13.1-2) ... Setting up python3-zipp (3.21.0-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up man-db (2.13.0-1) ... Not building database; man-db/auto-update is not 'true'. Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-more-itertools (10.6.0-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-typeguard (4.4.1-1) ... Setting up debhelper (13.24.1) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-jaraco.text (4.0.0-1) ... Setting up python3-pkg-resources (75.6.0-1) ... Setting up python3-setuptools (75.6.0-1) ... Setting up dh-python (6.20250108) ... Processing triggers for libc-bin (2.40-7) ... 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 I: Building the package I: Running cd /build/reproducible-path/python3-dmm-0.1.1/ && 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 > ../python3-dmm_0.1.1-1_source.changes dpkg-buildpackage: info: source package python3-dmm dpkg-buildpackage: info: source version 0.1.1-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Jonathan Carter dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --buildsystem=pybuild --with python3 dh_auto_clean -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py clean running clean removing '/build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --buildsystem=pybuild --with python3 dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm copying dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm copying dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm running egg_info creating dmm_highvoltage.egg-info writing dmm_highvoltage.egg-info/PKG-INFO writing dependency_links to dmm_highvoltage.egg-info/dependency_links.txt writing top-level names to dmm_highvoltage.egg-info/top_level.txt writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found anywhere in distribution writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'dmm.modules.aptpkg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptpkg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptpkg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptpkg' to be distributed and are already explicitly excluding 'dmm.modules.aptpkg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.aptsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptsetup' to be distributed and are already explicitly excluding 'dmm.modules.aptsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.cfdisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.cfdisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.cfdisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.cfdisk' to be distributed and are already explicitly excluding 'dmm.modules.cfdisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.checksums' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.checksums' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.checksums' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.checksums' to be distributed and are already explicitly excluding 'dmm.modules.checksums' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dd' to be distributed and are already explicitly excluding 'dmm.modules.dd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.debootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.debootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.debootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.debootstrap' to be distributed and are already explicitly excluding 'dmm.modules.debootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.download' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.download' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.download' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.download' to be distributed and are already explicitly excluding 'dmm.modules.download' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dpkgsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dpkgsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dpkgsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dpkgsetup' to be distributed and are already explicitly excluding 'dmm.modules.dpkgsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.fallocate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.fallocate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.fallocate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.fallocate' to be distributed and are already explicitly excluding 'dmm.modules.fallocate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.grub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.grub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.grub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.grub' to be distributed and are already explicitly excluding 'dmm.modules.grub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.linux' to be distributed and are already explicitly excluding 'dmm.modules.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.livedisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.livedisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.livedisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.livedisk' to be distributed and are already explicitly excluding 'dmm.modules.livedisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.losetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.losetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.losetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.losetup' to be distributed and are already explicitly excluding 'dmm.modules.losetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.lsblk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.lsblk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.lsblk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.lsblk' to be distributed and are already explicitly excluding 'dmm.modules.lsblk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mkfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mkfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mkfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mkfs' to be distributed and are already explicitly excluding 'dmm.modules.mkfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mmdebstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mmdebstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mmdebstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mmdebstrap' to be distributed and are already explicitly excluding 'dmm.modules.mmdebstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mountfs' to be distributed and are already explicitly excluding 'dmm.modules.mountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.networking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.networking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.networking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.networking' to be distributed and are already explicitly excluding 'dmm.modules.networking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.parted' to be distributed and are already explicitly excluding 'dmm.modules.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.readme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.readme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.readme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.readme' to be distributed and are already explicitly excluding 'dmm.modules.readme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.remove' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.remove' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.remove' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.remove' to be distributed and are already explicitly excluding 'dmm.modules.remove' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.reprepro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.reprepro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.reprepro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.reprepro' to be distributed and are already explicitly excluding 'dmm.modules.reprepro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.squashfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.squashfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.squashfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.squashfs' to be distributed and are already explicitly excluding 'dmm.modules.squashfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.umountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.umountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.umountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.umountfs' to be distributed and are already explicitly excluding 'dmm.modules.umountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.users' to be distributed and are already explicitly excluding 'dmm.modules.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.vmsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.vmsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.vmsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.vmsetup' to be distributed and are already explicitly excluding 'dmm.modules.vmsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.writefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.writefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.writefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.writefile' to be distributed and are already explicitly excluding 'dmm.modules.writefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.xorriso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.xorriso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.xorriso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.xorriso' to be distributed and are already explicitly excluding 'dmm.modules.xorriso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums copying dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums copying dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd copying dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd copying dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download copying dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate copying dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub copying dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux copying dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux copying dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk copying dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk copying dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup copying dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup copying dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk copying dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk copying dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs copying dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs copying dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs copying dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs copying dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking copying dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking copying dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted copying dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted copying dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme copying dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme copying dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove copying dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro copying dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs copying dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs copying dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs copying dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users copying dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users copying dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile copying dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso copying dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso copying dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build; python3.13 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s NO TESTS RAN create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python3-dmm-0.1.1/debian/tmp 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 dmm_highvoltage.egg-info/PKG-INFO writing dependency_links to dmm_highvoltage.egg-info/dependency_links.txt writing top-level names to dmm_highvoltage.egg-info/top_level.txt reading manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found anywhere in distribution writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'dmm.modules.aptpkg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptpkg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptpkg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptpkg' to be distributed and are already explicitly excluding 'dmm.modules.aptpkg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.aptsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptsetup' to be distributed and are already explicitly excluding 'dmm.modules.aptsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.cfdisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.cfdisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.cfdisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.cfdisk' to be distributed and are already explicitly excluding 'dmm.modules.cfdisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.checksums' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.checksums' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.checksums' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.checksums' to be distributed and are already explicitly excluding 'dmm.modules.checksums' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dd' to be distributed and are already explicitly excluding 'dmm.modules.dd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.debootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.debootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.debootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.debootstrap' to be distributed and are already explicitly excluding 'dmm.modules.debootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.download' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.download' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.download' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.download' to be distributed and are already explicitly excluding 'dmm.modules.download' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dpkgsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dpkgsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dpkgsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dpkgsetup' to be distributed and are already explicitly excluding 'dmm.modules.dpkgsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.fallocate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.fallocate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.fallocate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.fallocate' to be distributed and are already explicitly excluding 'dmm.modules.fallocate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.grub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.grub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.grub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.grub' to be distributed and are already explicitly excluding 'dmm.modules.grub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.linux' to be distributed and are already explicitly excluding 'dmm.modules.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.livedisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.livedisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.livedisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.livedisk' to be distributed and are already explicitly excluding 'dmm.modules.livedisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.losetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.losetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.losetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.losetup' to be distributed and are already explicitly excluding 'dmm.modules.losetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.lsblk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.lsblk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.lsblk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.lsblk' to be distributed and are already explicitly excluding 'dmm.modules.lsblk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mkfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mkfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mkfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mkfs' to be distributed and are already explicitly excluding 'dmm.modules.mkfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mmdebstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mmdebstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mmdebstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mmdebstrap' to be distributed and are already explicitly excluding 'dmm.modules.mmdebstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mountfs' to be distributed and are already explicitly excluding 'dmm.modules.mountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.networking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.networking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.networking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.networking' to be distributed and are already explicitly excluding 'dmm.modules.networking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.parted' to be distributed and are already explicitly excluding 'dmm.modules.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.readme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.readme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.readme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.readme' to be distributed and are already explicitly excluding 'dmm.modules.readme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.remove' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.remove' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.remove' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.remove' to be distributed and are already explicitly excluding 'dmm.modules.remove' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.reprepro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.reprepro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.reprepro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.reprepro' to be distributed and are already explicitly excluding 'dmm.modules.reprepro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.squashfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.squashfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.squashfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.squashfs' to be distributed and are already explicitly excluding 'dmm.modules.squashfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.umountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.umountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.umountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.umountfs' to be distributed and are already explicitly excluding 'dmm.modules.umountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.users' to be distributed and are already explicitly excluding 'dmm.modules.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.vmsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.vmsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.vmsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.vmsetup' to be distributed and are already explicitly excluding 'dmm.modules.vmsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.writefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.writefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.writefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.writefile' to be distributed and are already explicitly excluding 'dmm.modules.writefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.xorriso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.xorriso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.xorriso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.xorriso' to be distributed and are already explicitly excluding 'dmm.modules.xorriso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__pycache__ copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__pycache__ creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso/xorriso.py to xorriso.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile/writefile.py to writefile.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup/vmsetup.py to vmsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users/users.py to users.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs/umountfs.py to umountfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs/squashfs.py to squashfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro/reprepro.py to reprepro.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove/remove.py to remove.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme/readme.py to readme.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted/parted.py to parted.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking/networking.py to networking.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs/mountfs.py to mountfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap/mmdebstrap.py to mmdebstrap.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs/mkfs.py to mkfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk/lsblk.py to lsblk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup/losetup.py to losetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk/livedisk.py to livedisk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux/linux.py to linux.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub/grub.py to grub.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate/fallocate.py to fallocate.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup/dpkgsetup.py to dpkgsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download/download.py to download.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap/debootstrap.py to debootstrap.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd/dd.py to dd.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums/checksums.py to checksums.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk/cfdisk.py to cfdisk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup/aptsetup.py to aptsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg/aptpkg.py to aptpkg.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/dmm.py to dmm.cpython-313.pyc running install_egg_info Copying dmm_highvoltage.egg-info to /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm_highvoltage-0.0.2.egg-info Skipping SOURCES.txt running install_scripts dh_install -O--buildsystem=pybuild dh_installdocs -O--buildsystem=pybuild dh_installchangelogs -O--buildsystem=pybuild dh_python3 -O--buildsystem=pybuild dh_installsystemduser -O--buildsystem=pybuild dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild dh_compress -O--buildsystem=pybuild dh_fixperms -O--buildsystem=pybuild dh_missing -O--buildsystem=pybuild dh_installdeb -O--buildsystem=pybuild dh_gencontrol -O--buildsystem=pybuild dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-dmm' in '../python3-dmm_0.1.1-1_all.deb'. dpkg-deb: building package 'dmm-utils' in '../dmm-utils_0.1.1-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python3-dmm_0.1.1-1_arm64.buildinfo dpkg-genchanges --build=binary -O../python3-dmm_0.1.1-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/3301095 and its subdirectories I: Current time: Sat Feb 22 02:29:18 -12 2025 I: pbuilder-time-stamp: 1740234558 Sat Feb 22 14:29:18 UTC 2025 I: Signing ./b1/python3-dmm_0.1.1-1_arm64.buildinfo as python3-dmm_0.1.1-1_arm64.buildinfo.asc Sat Feb 22 14:29:18 UTC 2025 I: Signed ./b1/python3-dmm_0.1.1-1_arm64.buildinfo as ./b1/python3-dmm_0.1.1-1_arm64.buildinfo.asc Sat Feb 22 14:29:18 UTC 2025 - build #1 for python3-dmm/trixie/arm64 on codethink04-arm64 done. Starting cleanup. All cleanup done. Sat Feb 22 14:29:18 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-0pBrM0Er, removing. /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb: total 16 drwxr-xr-x 2 jenkins jenkins 4096 Feb 22 14:29 b1 drwxr-xr-x 2 jenkins jenkins 4096 Feb 22 14:28 b2 -rw-r--r-- 1 jenkins jenkins 2027 Feb 8 2023 python3-dmm_0.1.1-1.dsc -rw------- 1 jenkins jenkins 3161 Feb 22 14:28 rbuildlog.5IWN6DX /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b1: total 656 -rw-r--r-- 1 jenkins jenkins 178840 Feb 22 14:29 build.log -rw-r--r-- 1 jenkins jenkins 216984 Feb 22 14:29 dmm-utils_0.1.1-1_all.deb -rw-r--r-- 1 jenkins jenkins 2244 Feb 22 14:29 python3-dmm_0.1.1-1.debian.tar.xz -rw-r--r-- 1 jenkins jenkins 2027 Feb 22 14:29 python3-dmm_0.1.1-1.dsc -rw-r--r-- 1 jenkins jenkins 12224 Feb 22 14:29 python3-dmm_0.1.1-1_all.deb -rw-r--r-- 1 jenkins jenkins 5687 Feb 22 14:29 python3-dmm_0.1.1-1_arm64.buildinfo -rw-r--r-- 1 jenkins jenkins 6569 Feb 22 14:29 python3-dmm_0.1.1-1_arm64.buildinfo.asc -rw-r--r-- 1 jenkins jenkins 1424 Feb 22 14:29 python3-dmm_0.1.1-1_arm64.changes -rw-r--r-- 1 jenkins jenkins 1551 Feb 22 14:29 python3-dmm_0.1.1-1_source.changes -rw-r--r-- 1 jenkins jenkins 227377 Feb 22 14:29 python3-dmm_0.1.1.orig.tar.gz /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2: total 0 Sat Feb 22 14:29:19 UTC 2025 I: Deleting $TMPDIR on codethink04-arm64.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Sat Feb 22 02:28:42 -12 2025 I: pbuilder-time-stamp: 1740234522 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 [python3-dmm_0.1.1-1.dsc] I: copying [./python3-dmm_0.1.1.orig.tar.gz] I: copying [./python3-dmm_0.1.1-1.debian.tar.xz] I: Extracting source dpkg-source: warning: cannot verify inline signature for ./python3-dmm_0.1.1-1.dsc: unsupported subcommand dpkg-source: info: extracting python3-dmm in python3-dmm-0.1.1 dpkg-source: info: unpacking python3-dmm_0.1.1.orig.tar.gz dpkg-source: info: unpacking python3-dmm_0.1.1-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/3301095/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='b2363ea5bbf24a6dab6e738328e0bf29' 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='3301095' 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.yP0UuGAb/pbuilderrc_oxP6 --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.yP0UuGAb/b1 --logfile b1/build.log python3-dmm_0.1.1-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 codethink04-arm64 6.1.0-31-cloud-arm64 #1 SMP Debian 6.1.128-1 (2025-02-07) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Nov 22 14:40 /bin -> usr/bin I: user script /srv/workspace/pbuilder/3301095/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 (= 13), dh-python, python3-setuptools, python3 dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 19972 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 (= 13); 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-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3; however: Package python3 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} 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} libffi8{a} libfile-stripnondeterminism-perl{a} libicu72{a} libmagic-mgc{a} libmagic1t64{a} libpipeline1{a} libpython3-stdlib{a} libpython3.13-minimal{a} libpython3.13-stdlib{a} libreadline8t64{a} libtool{a} libuchardet0{a} libunistring5{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} po-debconf{a} python3{a} python3-autocommand{a} python3-inflect{a} python3-jaraco.context{a} python3-jaraco.functools{a} python3-jaraco.text{a} python3-minimal{a} python3-more-itertools{a} python3-pkg-resources{a} python3-setuptools{a} python3-typeguard{a} python3-typing-extensions{a} python3-zipp{a} python3.13{a} python3.13-minimal{a} readline-common{a} sensible-utils{a} tzdata{a} The following packages are RECOMMENDED but will NOT be installed: ca-certificates curl libarchive-cpio-perl libltdl-dev libmail-sendmail-perl lynx wget 0 packages upgraded, 56 newly installed, 0 to remove and 0 not upgraded. Need to get 27.6 MB of archives. After unpacking 114 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian trixie/main arm64 libpython3.13-minimal arm64 3.13.2-1 [853 kB] Get: 2 http://deb.debian.org/debian trixie/main arm64 libexpat1 arm64 2.6.4-1 [90.7 kB] Get: 3 http://deb.debian.org/debian trixie/main arm64 python3.13-minimal arm64 3.13.2-1 [1997 kB] Get: 4 http://deb.debian.org/debian trixie/main arm64 python3-minimal arm64 3.13.1-2 [27.0 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 2025a-2 [259 kB] Get: 8 http://deb.debian.org/debian trixie/main arm64 libffi8 arm64 3.4.7-1 [21.2 kB] Get: 9 http://deb.debian.org/debian trixie/main arm64 readline-common all 8.2-6 [69.4 kB] Get: 10 http://deb.debian.org/debian trixie/main arm64 libreadline8t64 arm64 8.2-6 [159 kB] Get: 11 http://deb.debian.org/debian trixie/main arm64 libpython3.13-stdlib arm64 3.13.2-1 [1914 kB] Get: 12 http://deb.debian.org/debian trixie/main arm64 python3.13 arm64 3.13.2-1 [745 kB] Get: 13 http://deb.debian.org/debian trixie/main arm64 libpython3-stdlib arm64 3.13.1-2 [9952 B] Get: 14 http://deb.debian.org/debian trixie/main arm64 python3 arm64 3.13.1-2 [28.0 kB] Get: 15 http://deb.debian.org/debian trixie/main arm64 sensible-utils all 0.0.24 [24.8 kB] Get: 16 http://deb.debian.org/debian trixie/main arm64 libmagic-mgc arm64 1:5.45-3+b1 [314 kB] Get: 17 http://deb.debian.org/debian trixie/main arm64 libmagic1t64 arm64 1:5.45-3+b1 [102 kB] Get: 18 http://deb.debian.org/debian trixie/main arm64 file arm64 1:5.45-3+b1 [43.4 kB] Get: 19 http://deb.debian.org/debian trixie/main arm64 gettext-base arm64 0.23.1-1 [241 kB] Get: 20 http://deb.debian.org/debian trixie/main arm64 libuchardet0 arm64 0.0.8-1+b2 [69.2 kB] Get: 21 http://deb.debian.org/debian trixie/main arm64 groff-base arm64 1.23.0-7 [1129 kB] Get: 22 http://deb.debian.org/debian trixie/main arm64 bsdextrautils arm64 2.40.4-3 [92.0 kB] Get: 23 http://deb.debian.org/debian trixie/main arm64 libpipeline1 arm64 1.5.8-1 [40.2 kB] Get: 24 http://deb.debian.org/debian trixie/main arm64 man-db arm64 2.13.0-1 [1404 kB] Get: 25 http://deb.debian.org/debian trixie/main arm64 m4 arm64 1.4.19-5 [284 kB] Get: 26 http://deb.debian.org/debian trixie/main arm64 autoconf all 2.72-3 [493 kB] Get: 27 http://deb.debian.org/debian trixie/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 28 http://deb.debian.org/debian trixie/main arm64 automake all 1:1.17-3 [862 kB] Get: 29 http://deb.debian.org/debian trixie/main arm64 autopoint all 0.23.1-1 [770 kB] Get: 30 http://deb.debian.org/debian trixie/main arm64 libdebhelper-perl all 13.24.1 [90.9 kB] Get: 31 http://deb.debian.org/debian trixie/main arm64 libtool all 2.5.4-3 [539 kB] Get: 32 http://deb.debian.org/debian trixie/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 33 http://deb.debian.org/debian trixie/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 34 http://deb.debian.org/debian trixie/main arm64 libfile-stripnondeterminism-perl all 1.14.1-2 [19.7 kB] Get: 35 http://deb.debian.org/debian trixie/main arm64 dh-strip-nondeterminism all 1.14.1-2 [8620 B] Get: 36 http://deb.debian.org/debian trixie/main arm64 libelf1t64 arm64 0.192-4 [189 kB] Get: 37 http://deb.debian.org/debian trixie/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 38 http://deb.debian.org/debian trixie/main arm64 libunistring5 arm64 1.3-1 [449 kB] Get: 39 http://deb.debian.org/debian trixie/main arm64 libicu72 arm64 72.1-6 [9239 kB] Get: 40 http://deb.debian.org/debian trixie/main arm64 libxml2 arm64 2.12.7+dfsg+really2.9.14-0.2+b1 [630 kB] Get: 41 http://deb.debian.org/debian trixie/main arm64 gettext arm64 0.23.1-1 [1610 kB] Get: 42 http://deb.debian.org/debian trixie/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 43 http://deb.debian.org/debian trixie/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 44 http://deb.debian.org/debian trixie/main arm64 debhelper all 13.24.1 [920 kB] Get: 45 http://deb.debian.org/debian trixie/main arm64 python3-autocommand all 2.2.2-3 [13.6 kB] Get: 46 http://deb.debian.org/debian trixie/main arm64 python3-more-itertools all 10.6.0-1 [65.3 kB] Get: 47 http://deb.debian.org/debian trixie/main arm64 python3-typing-extensions all 4.12.2-2 [73.0 kB] Get: 48 http://deb.debian.org/debian trixie/main arm64 python3-typeguard all 4.4.1-1 [37.0 kB] Get: 49 http://deb.debian.org/debian trixie/main arm64 python3-inflect all 7.3.1-2 [32.4 kB] Get: 50 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.context all 6.0.0-1 [7984 B] Get: 51 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.functools all 4.1.0-1 [12.0 kB] Get: 52 http://deb.debian.org/debian trixie/main arm64 python3-pkg-resources all 75.6.0-1 [222 kB] Get: 53 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.text all 4.0.0-1 [11.4 kB] Get: 54 http://deb.debian.org/debian trixie/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 55 http://deb.debian.org/debian trixie/main arm64 python3-setuptools all 75.6.0-1 [720 kB] Get: 56 http://deb.debian.org/debian trixie/main arm64 dh-python all 6.20250108 [113 kB] Fetched 27.6 MB in 0s (151 MB/s) Preconfiguring packages ... Selecting previously unselected package libpython3.13-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 ... 19972 files and directories currently installed.) Preparing to unpack .../libpython3.13-minimal_3.13.2-1_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.2-1) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.4-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.4-1) ... Selecting previously unselected package python3.13-minimal. Preparing to unpack .../python3.13-minimal_3.13.2-1_arm64.deb ... Unpacking python3.13-minimal (3.13.2-1) ... Setting up libpython3.13-minimal:arm64 (3.13.2-1) ... Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.13-minimal (3.13.2-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 ... 20306 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.13.1-2_arm64.deb ... Unpacking python3-minimal (3.13.1-2) ... 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_2025a-2_all.deb ... Unpacking tzdata (2025a-2) ... Selecting previously unselected package libffi8:arm64. Preparing to unpack .../4-libffi8_3.4.7-1_arm64.deb ... Unpacking libffi8:arm64 (3.4.7-1) ... Selecting previously unselected package readline-common. Preparing to unpack .../5-readline-common_8.2-6_all.deb ... Unpacking readline-common (8.2-6) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../6-libreadline8t64_8.2-6_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-6) ... Selecting previously unselected package libpython3.13-stdlib:arm64. Preparing to unpack .../7-libpython3.13-stdlib_3.13.2-1_arm64.deb ... Unpacking libpython3.13-stdlib:arm64 (3.13.2-1) ... Selecting previously unselected package python3.13. Preparing to unpack .../8-python3.13_3.13.2-1_arm64.deb ... Unpacking python3.13 (3.13.2-1) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../9-libpython3-stdlib_3.13.1-2_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3-minimal (3.13.1-2) ... 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 ... 21316 files and directories currently installed.) Preparing to unpack .../00-python3_3.13.1-2_arm64.deb ... Unpacking python3 (3.13.1-2) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../01-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../02-libmagic-mgc_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3+b1) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../03-libmagic1t64_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3+b1) ... Selecting previously unselected package file. Preparing to unpack .../04-file_1%3a5.45-3+b1_arm64.deb ... Unpacking file (1:5.45-3+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../05-gettext-base_0.23.1-1_arm64.deb ... Unpacking gettext-base (0.23.1-1) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../06-libuchardet0_0.0.8-1+b2_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b2) ... Selecting previously unselected package groff-base. Preparing to unpack .../07-groff-base_1.23.0-7_arm64.deb ... Unpacking groff-base (1.23.0-7) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../08-bsdextrautils_2.40.4-3_arm64.deb ... Unpacking bsdextrautils (2.40.4-3) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../09-libpipeline1_1.5.8-1_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../10-man-db_2.13.0-1_arm64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../11-m4_1.4.19-5_arm64.deb ... Unpacking m4 (1.4.19-5) ... Selecting previously unselected package autoconf. Preparing to unpack .../12-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../13-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../14-automake_1%3a1.17-3_all.deb ... Unpacking automake (1:1.17-3) ... Selecting previously unselected package autopoint. Preparing to unpack .../15-autopoint_0.23.1-1_all.deb ... Unpacking autopoint (0.23.1-1) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../16-libdebhelper-perl_13.24.1_all.deb ... Unpacking libdebhelper-perl (13.24.1) ... Selecting previously unselected package libtool. Preparing to unpack .../17-libtool_2.5.4-3_all.deb ... Unpacking libtool (2.5.4-3) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../18-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../19-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../20-libfile-stripnondeterminism-perl_1.14.1-2_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.1-2) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../21-dh-strip-nondeterminism_1.14.1-2_all.deb ... Unpacking dh-strip-nondeterminism (1.14.1-2) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../22-libelf1t64_0.192-4_arm64.deb ... Unpacking libelf1t64:arm64 (0.192-4) ... Selecting previously unselected package dwz. Preparing to unpack .../23-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libunistring5:arm64. Preparing to unpack .../24-libunistring5_1.3-1_arm64.deb ... Unpacking libunistring5:arm64 (1.3-1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../25-libicu72_72.1-6_arm64.deb ... Unpacking libicu72:arm64 (72.1-6) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../26-libxml2_2.12.7+dfsg+really2.9.14-0.2+b1_arm64.deb ... Unpacking libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Selecting previously unselected package gettext. Preparing to unpack .../27-gettext_0.23.1-1_arm64.deb ... Unpacking gettext (0.23.1-1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../28-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 .../29-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../30-debhelper_13.24.1_all.deb ... Unpacking debhelper (13.24.1) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../31-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../32-python3-more-itertools_10.6.0-1_all.deb ... Unpacking python3-more-itertools (10.6.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../33-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../34-python3-typeguard_4.4.1-1_all.deb ... Unpacking python3-typeguard (4.4.1-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../35-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../36-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../37-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../38-python3-pkg-resources_75.6.0-1_all.deb ... Unpacking python3-pkg-resources (75.6.0-1) ... Selecting previously unselected package python3-jaraco.text. Preparing to unpack .../39-python3-jaraco.text_4.0.0-1_all.deb ... Unpacking python3-jaraco.text (4.0.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../40-python3-zipp_3.21.0-1_all.deb ... Unpacking python3-zipp (3.21.0-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../41-python3-setuptools_75.6.0-1_all.deb ... Unpacking python3-setuptools (75.6.0-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../42-dh-python_6.20250108_all.deb ... Unpacking dh-python (6.20250108) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.8-1) ... Setting up libicu72:arm64 (72.1-6) ... Setting up bsdextrautils (2.40.4-3) ... Setting up libmagic-mgc (1:5.45-3+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.24.1) ... Setting up libmagic1t64:arm64 (1:5.45-3+b1) ... Setting up gettext-base (0.23.1-1) ... Setting up m4 (1.4.19-5) ... Setting up file (1:5.45-3+b1) ... Setting up libelf1t64:arm64 (0.192-4) ... Setting up tzdata (2025a-2) ... Current default time zone: 'Etc/UTC' Local time is now: Sat Feb 22 14:29:03 UTC 2025. Universal Time is now: Sat Feb 22 14:29:03 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up libunistring5:arm64 (1.3-1) ... Setting up autopoint (0.23.1-1) ... Setting up autoconf (2.72-3) ... Setting up libffi8:arm64 (3.4.7-1) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libuchardet0:arm64 (0.0.8-1+b2) ... Setting up netbase (6.4) ... Setting up readline-common (8.2-6) ... Setting up libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Setting up automake (1:1.17-3) ... update-alternatives: using /usr/bin/automake-1.17 to provide /usr/bin/automake (automake) in auto mode Setting up libfile-stripnondeterminism-perl (1.14.1-2) ... Setting up gettext (0.23.1-1) ... Setting up libtool (2.5.4-3) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up libreadline8t64:arm64 (8.2-6) ... Setting up dh-strip-nondeterminism (1.14.1-2) ... Setting up groff-base (1.23.0-7) ... Setting up libpython3.13-stdlib:arm64 (3.13.2-1) ... Setting up libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3.13 (3.13.2-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up python3 (3.13.1-2) ... Setting up python3-zipp (3.21.0-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up man-db (2.13.0-1) ... Not building database; man-db/auto-update is not 'true'. Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-more-itertools (10.6.0-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-typeguard (4.4.1-1) ... Setting up debhelper (13.24.1) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-jaraco.text (4.0.0-1) ... Setting up python3-pkg-resources (75.6.0-1) ... Setting up python3-setuptools (75.6.0-1) ... Setting up dh-python (6.20250108) ... Processing triggers for libc-bin (2.40-7) ... 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 I: Building the package I: Running cd /build/reproducible-path/python3-dmm-0.1.1/ && 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 > ../python3-dmm_0.1.1-1_source.changes dpkg-buildpackage: info: source package python3-dmm dpkg-buildpackage: info: source version 0.1.1-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Jonathan Carter dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --buildsystem=pybuild --with python3 dh_auto_clean -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py clean running clean removing '/build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --buildsystem=pybuild --with python3 dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm copying dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm copying dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm running egg_info creating dmm_highvoltage.egg-info writing dmm_highvoltage.egg-info/PKG-INFO writing dependency_links to dmm_highvoltage.egg-info/dependency_links.txt writing top-level names to dmm_highvoltage.egg-info/top_level.txt writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found anywhere in distribution writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'dmm.modules.aptpkg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptpkg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptpkg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptpkg' to be distributed and are already explicitly excluding 'dmm.modules.aptpkg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.aptsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptsetup' to be distributed and are already explicitly excluding 'dmm.modules.aptsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.cfdisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.cfdisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.cfdisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.cfdisk' to be distributed and are already explicitly excluding 'dmm.modules.cfdisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.checksums' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.checksums' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.checksums' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.checksums' to be distributed and are already explicitly excluding 'dmm.modules.checksums' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dd' to be distributed and are already explicitly excluding 'dmm.modules.dd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.debootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.debootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.debootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.debootstrap' to be distributed and are already explicitly excluding 'dmm.modules.debootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.download' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.download' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.download' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.download' to be distributed and are already explicitly excluding 'dmm.modules.download' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dpkgsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dpkgsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dpkgsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dpkgsetup' to be distributed and are already explicitly excluding 'dmm.modules.dpkgsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.fallocate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.fallocate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.fallocate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.fallocate' to be distributed and are already explicitly excluding 'dmm.modules.fallocate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.grub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.grub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.grub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.grub' to be distributed and are already explicitly excluding 'dmm.modules.grub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.linux' to be distributed and are already explicitly excluding 'dmm.modules.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.livedisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.livedisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.livedisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.livedisk' to be distributed and are already explicitly excluding 'dmm.modules.livedisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.losetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.losetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.losetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.losetup' to be distributed and are already explicitly excluding 'dmm.modules.losetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.lsblk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.lsblk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.lsblk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.lsblk' to be distributed and are already explicitly excluding 'dmm.modules.lsblk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mkfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mkfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mkfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mkfs' to be distributed and are already explicitly excluding 'dmm.modules.mkfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mmdebstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mmdebstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mmdebstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mmdebstrap' to be distributed and are already explicitly excluding 'dmm.modules.mmdebstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mountfs' to be distributed and are already explicitly excluding 'dmm.modules.mountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.networking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.networking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.networking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.networking' to be distributed and are already explicitly excluding 'dmm.modules.networking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.parted' to be distributed and are already explicitly excluding 'dmm.modules.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.readme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.readme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.readme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.readme' to be distributed and are already explicitly excluding 'dmm.modules.readme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.remove' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.remove' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.remove' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.remove' to be distributed and are already explicitly excluding 'dmm.modules.remove' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.reprepro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.reprepro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.reprepro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.reprepro' to be distributed and are already explicitly excluding 'dmm.modules.reprepro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.squashfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.squashfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.squashfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.squashfs' to be distributed and are already explicitly excluding 'dmm.modules.squashfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.umountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.umountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.umountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.umountfs' to be distributed and are already explicitly excluding 'dmm.modules.umountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.users' to be distributed and are already explicitly excluding 'dmm.modules.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.vmsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.vmsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.vmsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.vmsetup' to be distributed and are already explicitly excluding 'dmm.modules.vmsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.writefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.writefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.writefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.writefile' to be distributed and are already explicitly excluding 'dmm.modules.writefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.xorriso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.xorriso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.xorriso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.xorriso' to be distributed and are already explicitly excluding 'dmm.modules.xorriso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums copying dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums copying dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd copying dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd copying dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download copying dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate copying dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub copying dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux copying dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux copying dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk copying dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk copying dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup copying dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup copying dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk copying dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk copying dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs copying dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs copying dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs copying dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs copying dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking copying dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking copying dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted copying dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted copying dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme copying dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme copying dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove copying dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro copying dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs copying dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs copying dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs copying dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users copying dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users copying dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile copying dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso copying dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso copying dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build; python3.13 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s NO TESTS RAN create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python3-dmm-0.1.1/debian/tmp 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 dmm_highvoltage.egg-info/PKG-INFO writing dependency_links to dmm_highvoltage.egg-info/dependency_links.txt writing top-level names to dmm_highvoltage.egg-info/top_level.txt reading manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found anywhere in distribution writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'dmm.modules.aptpkg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptpkg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptpkg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptpkg' to be distributed and are already explicitly excluding 'dmm.modules.aptpkg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.aptsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptsetup' to be distributed and are already explicitly excluding 'dmm.modules.aptsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.cfdisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.cfdisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.cfdisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.cfdisk' to be distributed and are already explicitly excluding 'dmm.modules.cfdisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.checksums' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.checksums' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.checksums' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.checksums' to be distributed and are already explicitly excluding 'dmm.modules.checksums' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dd' to be distributed and are already explicitly excluding 'dmm.modules.dd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.debootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.debootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.debootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.debootstrap' to be distributed and are already explicitly excluding 'dmm.modules.debootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.download' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.download' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.download' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.download' to be distributed and are already explicitly excluding 'dmm.modules.download' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dpkgsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dpkgsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dpkgsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dpkgsetup' to be distributed and are already explicitly excluding 'dmm.modules.dpkgsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.fallocate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.fallocate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.fallocate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.fallocate' to be distributed and are already explicitly excluding 'dmm.modules.fallocate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.grub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.grub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.grub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.grub' to be distributed and are already explicitly excluding 'dmm.modules.grub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.linux' to be distributed and are already explicitly excluding 'dmm.modules.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.livedisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.livedisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.livedisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.livedisk' to be distributed and are already explicitly excluding 'dmm.modules.livedisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.losetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.losetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.losetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.losetup' to be distributed and are already explicitly excluding 'dmm.modules.losetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.lsblk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.lsblk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.lsblk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.lsblk' to be distributed and are already explicitly excluding 'dmm.modules.lsblk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mkfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mkfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mkfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mkfs' to be distributed and are already explicitly excluding 'dmm.modules.mkfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mmdebstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mmdebstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mmdebstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mmdebstrap' to be distributed and are already explicitly excluding 'dmm.modules.mmdebstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mountfs' to be distributed and are already explicitly excluding 'dmm.modules.mountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.networking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.networking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.networking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.networking' to be distributed and are already explicitly excluding 'dmm.modules.networking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.parted' to be distributed and are already explicitly excluding 'dmm.modules.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.readme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.readme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.readme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.readme' to be distributed and are already explicitly excluding 'dmm.modules.readme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.remove' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.remove' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.remove' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.remove' to be distributed and are already explicitly excluding 'dmm.modules.remove' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.reprepro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.reprepro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.reprepro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.reprepro' to be distributed and are already explicitly excluding 'dmm.modules.reprepro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.squashfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.squashfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.squashfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.squashfs' to be distributed and are already explicitly excluding 'dmm.modules.squashfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.umountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.umountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.umountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.umountfs' to be distributed and are already explicitly excluding 'dmm.modules.umountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.users' to be distributed and are already explicitly excluding 'dmm.modules.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.vmsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.vmsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.vmsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.vmsetup' to be distributed and are already explicitly excluding 'dmm.modules.vmsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.writefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.writefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.writefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.writefile' to be distributed and are already explicitly excluding 'dmm.modules.writefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.xorriso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.xorriso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.xorriso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.xorriso' to be distributed and are already explicitly excluding 'dmm.modules.xorriso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__pycache__ copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__pycache__ creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso/xorriso.py to xorriso.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile/writefile.py to writefile.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup/vmsetup.py to vmsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users/users.py to users.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs/umountfs.py to umountfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs/squashfs.py to squashfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro/reprepro.py to reprepro.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove/remove.py to remove.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme/readme.py to readme.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted/parted.py to parted.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking/networking.py to networking.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs/mountfs.py to mountfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap/mmdebstrap.py to mmdebstrap.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs/mkfs.py to mkfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk/lsblk.py to lsblk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup/losetup.py to losetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk/livedisk.py to livedisk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux/linux.py to linux.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub/grub.py to grub.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate/fallocate.py to fallocate.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup/dpkgsetup.py to dpkgsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download/download.py to download.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap/debootstrap.py to debootstrap.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd/dd.py to dd.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums/checksums.py to checksums.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk/cfdisk.py to cfdisk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup/aptsetup.py to aptsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg/aptpkg.py to aptpkg.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/dmm.py to dmm.cpython-313.pyc running install_egg_info Copying dmm_highvoltage.egg-info to /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm_highvoltage-0.0.2.egg-info Skipping SOURCES.txt running install_scripts dh_install -O--buildsystem=pybuild dh_installdocs -O--buildsystem=pybuild dh_installchangelogs -O--buildsystem=pybuild dh_python3 -O--buildsystem=pybuild dh_installsystemduser -O--buildsystem=pybuild dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild dh_compress -O--buildsystem=pybuild dh_fixperms -O--buildsystem=pybuild dh_missing -O--buildsystem=pybuild dh_installdeb -O--buildsystem=pybuild dh_gencontrol -O--buildsystem=pybuild dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-dmm' in '../python3-dmm_0.1.1-1_all.deb'. dpkg-deb: building package 'dmm-utils' in '../dmm-utils_0.1.1-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python3-dmm_0.1.1-1_arm64.buildinfo dpkg-genchanges --build=binary -O../python3-dmm_0.1.1-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/3301095 and its subdirectories I: Current time: Sat Feb 22 02:29:18 -12 2025 I: pbuilder-time-stamp: 1740234558 Sat Feb 22 14:29:20 UTC 2025 I: 1st build successful. Starting 2nd build on remote node codethink03-arm64.debian.net. Sat Feb 22 14:29:20 UTC 2025 I: Preparing to do remote build '2' on codethink03-arm64.debian.net. Sat Feb 22 14:29:20 UTC 2025 - checking /var/lib/jenkins/offline_nodes if codethink03-arm64.debian.net is marked as down. Sat Feb 22 14:29:20 UTC 2025 - checking via ssh if codethink03-arm64.debian.net is up. removed '/tmp/read-only-fs-test-NcXpWk' ==================================================================================== Fri Mar 27 20:52:22 UTC 2026 - running /srv/jenkins/bin/reproducible_build.sh (for job /srv/jenkins/bin/reproducible_build.sh) on codethink03-arm64, called using "2 python3-dmm trixie /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb 0.1.1-1" as arguments. Fri Mar 27 20:52:22 UTC 2026 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-hiWWaeoe" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Fri Mar 27 20:52:22 UTC 2026 I: Downloading source for trixie/python3-dmm=0.1.1-1 Reading package lists... NOTICE: 'python3-dmm' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/jcc/distribution-management-modules.git Please use: git clone https://salsa.debian.org/jcc/distribution-management-modules.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 232 kB of source archives. Get:1 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (dsc) [2027 B] Get:2 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (tar) [227 kB] Get:3 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (diff) [2244 B] Fetched 232 kB in 0s (12.1 MB/s) Download complete and in download only mode Reading package lists... NOTICE: 'python3-dmm' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/jcc/distribution-management-modules.git Please use: git clone https://salsa.debian.org/jcc/distribution-management-modules.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 232 kB of source archives. Get:1 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (dsc) [2027 B] Get:2 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (tar) [227 kB] Get:3 http://deb.debian.org/debian trixie/main python3-dmm 0.1.1-1 (diff) [2244 B] Fetched 232 kB in 0s (12.1 MB/s) Download complete and in download only mode ============================================================================= Re-Building python3-dmm in trixie on arm64 on codethink03-arm64 now. Date: Fri Mar 27 20:52:22 GMT 2026 Date UTC: Fri Mar 27 20:52:22 UTC 2026 ============================================================================= ++ mktemp -t pbuilderrc_XXXX --tmpdir=/srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb + local TMPCFG=/srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/pbuilderrc_24aV + case ${ARCH} in + case $ARCH in + locale=nl_BE + language=nl + case "${SUITE}" in + reproducible_buildflags=+all + extra_deb_build_options= + case "${SRCPACKAGE}" in + cat + echo BUILDDIR=/build/reproducible-path + '[' python3-dmm = debian-installer -o python3-dmm = debian-installer-netboot-images ']' + pbuilder_options=() + local pbuilder_options + DEBBUILDOPTS=-b + BINARYTARGET= + '[' python3-dmm = u-boot ']' + case "${SRCPACKAGE}" in + PBUILDERTIMEOUT=24 + local PRESULT=0 + sudo timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/pbuilderrc_24aV --distribution trixie --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/trixie-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2 --logfile b2/build.log python3-dmm_0.1.1-1.dsc W: /root/.pbuilderrc does not exist I: Logging to b2/build.log I: pbuilder: network access will be disabled during build I: Current time: Sat Mar 28 10:52:22 +14 2026 I: pbuilder-time-stamp: 1774644742 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 [python3-dmm_0.1.1-1.dsc] I: copying [./python3-dmm_0.1.1.orig.tar.gz] I: copying [./python3-dmm_0.1.1-1.debian.tar.xz] I: Extracting source dpkg-source: warning: cannot verify inline signature for ./python3-dmm_0.1.1-1.dsc: unsupported subcommand dpkg-source: info: extracting python3-dmm in python3-dmm-0.1.1 dpkg-source: info: unpacking python3-dmm_0.1.1.orig.tar.gz dpkg-source: info: unpacking python3-dmm_0.1.1-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/61748/tmp/hooks/D01_modify_environment starting debug: Running on codethink03-arm64. I: Changing host+domainname to test build reproducibility I: Adding a custom variable just for the fun of it... I: Changing /bin/sh to bash '/bin/sh' -> '/bin/bash' lrwxrwxrwx 1 root root 9 Mar 27 20:52 /bin/sh -> /bin/bash I: Setting pbuilder2's login shell to /bin/bash I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other I: user script /srv/workspace/pbuilder/61748/tmp/hooks/D01_modify_environment finished I: user script /srv/workspace/pbuilder/61748/tmp/hooks/D02_print_environment starting I: set BASH=/bin/sh BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:globskipdots:hostcomplete:interactive_comments:patsub_replacement:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_LINENO=([0]="12" [1]="0") BASH_LOADABLES_PATH=/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib/bash:. BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") BASH_VERSINFO=([0]="5" [1]="2" [2]="37" [3]="1" [4]="release" [5]="aarch64-unknown-linux-gnu") BASH_VERSION='5.2.37(1)-release' BUILDDIR=/build/reproducible-path BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' BUILDUSERNAME=pbuilder2 BUILD_ARCH=arm64 DEBIAN_FRONTEND=noninteractive DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' DIRSTACK=() DISTRIBUTION=trixie EUID=0 FUNCNAME=([0]="Echo" [1]="main") GROUPS=() HOME=/root HOSTNAME=i-capture-the-hostname HOSTTYPE=aarch64 HOST_ARCH=arm64 IFS=' ' INVOCATION_ID=96fb3e1ed60944508b2d9c9a24da5086 LANG=C LANGUAGE=nl_BE:nl LC_ALL=C MACHTYPE=aarch64-unknown-linux-gnu MAIL=/var/mail/root OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path PBCURRENTCOMMANDLINEOPERATION=build PBUILDER_OPERATION=build PBUILDER_PKGDATADIR=/usr/share/pbuilder PBUILDER_PKGLIBDIR=/usr/lib/pbuilder PBUILDER_SYSCONFDIR=/etc PIPESTATUS=([0]="0") POSIXLY_CORRECT=y PPID=61748 PS4='+ ' PWD=/ SHELL=/bin/bash SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix SHLVL=3 SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/pbuilderrc_24aV --distribution trixie --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/trixie-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2 --logfile b2/build.log python3-dmm_0.1.1-1.dsc' SUDO_GID=109 SUDO_UID=104 SUDO_USER=jenkins TERM=unknown TZ=/usr/share/zoneinfo/Etc/GMT-14 UID=0 USER=root _='I: set' http_proxy=http://192.168.101.4:3128 I: uname -a Linux i-capture-the-hostname 6.1.0-31-cloud-arm64 #1 SMP Debian 6.1.128-1 (2025-02-07) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Nov 22 2024 /bin -> usr/bin I: user script /srv/workspace/pbuilder/61748/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 (= 13), dh-python, python3-setuptools, python3 dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 19922 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 (= 13); 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-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3; however: Package python3 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} 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} libffi8{a} libfile-stripnondeterminism-perl{a} libicu72{a} libmagic-mgc{a} libmagic1t64{a} libpipeline1{a} libpython3-stdlib{a} libpython3.13-minimal{a} libpython3.13-stdlib{a} libreadline8t64{a} libtool{a} libuchardet0{a} libunistring5{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} po-debconf{a} python3{a} python3-autocommand{a} python3-inflect{a} python3-jaraco.context{a} python3-jaraco.functools{a} python3-jaraco.text{a} python3-minimal{a} python3-more-itertools{a} python3-pkg-resources{a} python3-setuptools{a} python3-typeguard{a} python3-typing-extensions{a} python3-zipp{a} python3.13{a} python3.13-minimal{a} readline-common{a} sensible-utils{a} tzdata{a} The following packages are RECOMMENDED but will NOT be installed: ca-certificates curl libarchive-cpio-perl libltdl-dev libmail-sendmail-perl lynx wget 0 packages upgraded, 56 newly installed, 0 to remove and 0 not upgraded. Need to get 27.6 MB of archives. After unpacking 114 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian trixie/main arm64 libpython3.13-minimal arm64 3.13.2-1 [853 kB] Get: 2 http://deb.debian.org/debian trixie/main arm64 libexpat1 arm64 2.6.4-1 [90.7 kB] Get: 3 http://deb.debian.org/debian trixie/main arm64 python3.13-minimal arm64 3.13.2-1 [1997 kB] Get: 4 http://deb.debian.org/debian trixie/main arm64 python3-minimal arm64 3.13.1-2 [27.0 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 2025a-2 [259 kB] Get: 8 http://deb.debian.org/debian trixie/main arm64 libffi8 arm64 3.4.7-1 [21.2 kB] Get: 9 http://deb.debian.org/debian trixie/main arm64 readline-common all 8.2-6 [69.4 kB] Get: 10 http://deb.debian.org/debian trixie/main arm64 libreadline8t64 arm64 8.2-6 [159 kB] Get: 11 http://deb.debian.org/debian trixie/main arm64 libpython3.13-stdlib arm64 3.13.2-1 [1914 kB] Get: 12 http://deb.debian.org/debian trixie/main arm64 python3.13 arm64 3.13.2-1 [745 kB] Get: 13 http://deb.debian.org/debian trixie/main arm64 libpython3-stdlib arm64 3.13.1-2 [9952 B] Get: 14 http://deb.debian.org/debian trixie/main arm64 python3 arm64 3.13.1-2 [28.0 kB] Get: 15 http://deb.debian.org/debian trixie/main arm64 sensible-utils all 0.0.24 [24.8 kB] Get: 16 http://deb.debian.org/debian trixie/main arm64 libmagic-mgc arm64 1:5.45-3+b1 [314 kB] Get: 17 http://deb.debian.org/debian trixie/main arm64 libmagic1t64 arm64 1:5.45-3+b1 [102 kB] Get: 18 http://deb.debian.org/debian trixie/main arm64 file arm64 1:5.45-3+b1 [43.4 kB] Get: 19 http://deb.debian.org/debian trixie/main arm64 gettext-base arm64 0.23.1-1 [241 kB] Get: 20 http://deb.debian.org/debian trixie/main arm64 libuchardet0 arm64 0.0.8-1+b2 [69.2 kB] Get: 21 http://deb.debian.org/debian trixie/main arm64 groff-base arm64 1.23.0-7 [1129 kB] Get: 22 http://deb.debian.org/debian trixie/main arm64 bsdextrautils arm64 2.40.4-3 [92.0 kB] Get: 23 http://deb.debian.org/debian trixie/main arm64 libpipeline1 arm64 1.5.8-1 [40.2 kB] Get: 24 http://deb.debian.org/debian trixie/main arm64 man-db arm64 2.13.0-1 [1404 kB] Get: 25 http://deb.debian.org/debian trixie/main arm64 m4 arm64 1.4.19-5 [284 kB] Get: 26 http://deb.debian.org/debian trixie/main arm64 autoconf all 2.72-3 [493 kB] Get: 27 http://deb.debian.org/debian trixie/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 28 http://deb.debian.org/debian trixie/main arm64 automake all 1:1.17-3 [862 kB] Get: 29 http://deb.debian.org/debian trixie/main arm64 autopoint all 0.23.1-1 [770 kB] Get: 30 http://deb.debian.org/debian trixie/main arm64 libdebhelper-perl all 13.24.1 [90.9 kB] Get: 31 http://deb.debian.org/debian trixie/main arm64 libtool all 2.5.4-3 [539 kB] Get: 32 http://deb.debian.org/debian trixie/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 33 http://deb.debian.org/debian trixie/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 34 http://deb.debian.org/debian trixie/main arm64 libfile-stripnondeterminism-perl all 1.14.1-2 [19.7 kB] Get: 35 http://deb.debian.org/debian trixie/main arm64 dh-strip-nondeterminism all 1.14.1-2 [8620 B] Get: 36 http://deb.debian.org/debian trixie/main arm64 libelf1t64 arm64 0.192-4 [189 kB] Get: 37 http://deb.debian.org/debian trixie/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 38 http://deb.debian.org/debian trixie/main arm64 libunistring5 arm64 1.3-1 [449 kB] Get: 39 http://deb.debian.org/debian trixie/main arm64 libicu72 arm64 72.1-6 [9239 kB] Get: 40 http://deb.debian.org/debian trixie/main arm64 libxml2 arm64 2.12.7+dfsg+really2.9.14-0.2+b1 [630 kB] Get: 41 http://deb.debian.org/debian trixie/main arm64 gettext arm64 0.23.1-1 [1610 kB] Get: 42 http://deb.debian.org/debian trixie/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 43 http://deb.debian.org/debian trixie/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 44 http://deb.debian.org/debian trixie/main arm64 debhelper all 13.24.1 [920 kB] Get: 45 http://deb.debian.org/debian trixie/main arm64 python3-autocommand all 2.2.2-3 [13.6 kB] Get: 46 http://deb.debian.org/debian trixie/main arm64 python3-more-itertools all 10.6.0-1 [65.3 kB] Get: 47 http://deb.debian.org/debian trixie/main arm64 python3-typing-extensions all 4.12.2-2 [73.0 kB] Get: 48 http://deb.debian.org/debian trixie/main arm64 python3-typeguard all 4.4.1-1 [37.0 kB] Get: 49 http://deb.debian.org/debian trixie/main arm64 python3-inflect all 7.3.1-2 [32.4 kB] Get: 50 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.context all 6.0.0-1 [7984 B] Get: 51 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.functools all 4.1.0-1 [12.0 kB] Get: 52 http://deb.debian.org/debian trixie/main arm64 python3-pkg-resources all 75.6.0-1 [222 kB] Get: 53 http://deb.debian.org/debian trixie/main arm64 python3-jaraco.text all 4.0.0-1 [11.4 kB] Get: 54 http://deb.debian.org/debian trixie/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 55 http://deb.debian.org/debian trixie/main arm64 python3-setuptools all 75.6.0-1 [720 kB] Get: 56 http://deb.debian.org/debian trixie/main arm64 dh-python all 6.20250108 [113 kB] Fetched 27.6 MB in 0s (106 MB/s) Preconfiguring packages ... Selecting previously unselected package libpython3.13-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 ... 19922 files and directories currently installed.) Preparing to unpack .../libpython3.13-minimal_3.13.2-1_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.2-1) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.4-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.4-1) ... Selecting previously unselected package python3.13-minimal. Preparing to unpack .../python3.13-minimal_3.13.2-1_arm64.deb ... Unpacking python3.13-minimal (3.13.2-1) ... Setting up libpython3.13-minimal:arm64 (3.13.2-1) ... Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.13-minimal (3.13.2-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 ... 20256 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.13.1-2_arm64.deb ... Unpacking python3-minimal (3.13.1-2) ... 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_2025a-2_all.deb ... Unpacking tzdata (2025a-2) ... Selecting previously unselected package libffi8:arm64. Preparing to unpack .../4-libffi8_3.4.7-1_arm64.deb ... Unpacking libffi8:arm64 (3.4.7-1) ... Selecting previously unselected package readline-common. Preparing to unpack .../5-readline-common_8.2-6_all.deb ... Unpacking readline-common (8.2-6) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../6-libreadline8t64_8.2-6_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-6) ... Selecting previously unselected package libpython3.13-stdlib:arm64. Preparing to unpack .../7-libpython3.13-stdlib_3.13.2-1_arm64.deb ... Unpacking libpython3.13-stdlib:arm64 (3.13.2-1) ... Selecting previously unselected package python3.13. Preparing to unpack .../8-python3.13_3.13.2-1_arm64.deb ... Unpacking python3.13 (3.13.2-1) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../9-libpython3-stdlib_3.13.1-2_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3-minimal (3.13.1-2) ... 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 ... 21266 files and directories currently installed.) Preparing to unpack .../00-python3_3.13.1-2_arm64.deb ... Unpacking python3 (3.13.1-2) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../01-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../02-libmagic-mgc_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3+b1) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../03-libmagic1t64_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3+b1) ... Selecting previously unselected package file. Preparing to unpack .../04-file_1%3a5.45-3+b1_arm64.deb ... Unpacking file (1:5.45-3+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../05-gettext-base_0.23.1-1_arm64.deb ... Unpacking gettext-base (0.23.1-1) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../06-libuchardet0_0.0.8-1+b2_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b2) ... Selecting previously unselected package groff-base. Preparing to unpack .../07-groff-base_1.23.0-7_arm64.deb ... Unpacking groff-base (1.23.0-7) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../08-bsdextrautils_2.40.4-3_arm64.deb ... Unpacking bsdextrautils (2.40.4-3) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../09-libpipeline1_1.5.8-1_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../10-man-db_2.13.0-1_arm64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../11-m4_1.4.19-5_arm64.deb ... Unpacking m4 (1.4.19-5) ... Selecting previously unselected package autoconf. Preparing to unpack .../12-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../13-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../14-automake_1%3a1.17-3_all.deb ... Unpacking automake (1:1.17-3) ... Selecting previously unselected package autopoint. Preparing to unpack .../15-autopoint_0.23.1-1_all.deb ... Unpacking autopoint (0.23.1-1) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../16-libdebhelper-perl_13.24.1_all.deb ... Unpacking libdebhelper-perl (13.24.1) ... Selecting previously unselected package libtool. Preparing to unpack .../17-libtool_2.5.4-3_all.deb ... Unpacking libtool (2.5.4-3) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../18-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../19-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../20-libfile-stripnondeterminism-perl_1.14.1-2_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.1-2) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../21-dh-strip-nondeterminism_1.14.1-2_all.deb ... Unpacking dh-strip-nondeterminism (1.14.1-2) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../22-libelf1t64_0.192-4_arm64.deb ... Unpacking libelf1t64:arm64 (0.192-4) ... Selecting previously unselected package dwz. Preparing to unpack .../23-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libunistring5:arm64. Preparing to unpack .../24-libunistring5_1.3-1_arm64.deb ... Unpacking libunistring5:arm64 (1.3-1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../25-libicu72_72.1-6_arm64.deb ... Unpacking libicu72:arm64 (72.1-6) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../26-libxml2_2.12.7+dfsg+really2.9.14-0.2+b1_arm64.deb ... Unpacking libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Selecting previously unselected package gettext. Preparing to unpack .../27-gettext_0.23.1-1_arm64.deb ... Unpacking gettext (0.23.1-1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../28-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 .../29-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../30-debhelper_13.24.1_all.deb ... Unpacking debhelper (13.24.1) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../31-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../32-python3-more-itertools_10.6.0-1_all.deb ... Unpacking python3-more-itertools (10.6.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../33-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../34-python3-typeguard_4.4.1-1_all.deb ... Unpacking python3-typeguard (4.4.1-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../35-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../36-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../37-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../38-python3-pkg-resources_75.6.0-1_all.deb ... Unpacking python3-pkg-resources (75.6.0-1) ... Selecting previously unselected package python3-jaraco.text. Preparing to unpack .../39-python3-jaraco.text_4.0.0-1_all.deb ... Unpacking python3-jaraco.text (4.0.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../40-python3-zipp_3.21.0-1_all.deb ... Unpacking python3-zipp (3.21.0-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../41-python3-setuptools_75.6.0-1_all.deb ... Unpacking python3-setuptools (75.6.0-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../42-dh-python_6.20250108_all.deb ... Unpacking dh-python (6.20250108) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.8-1) ... Setting up libicu72:arm64 (72.1-6) ... Setting up bsdextrautils (2.40.4-3) ... Setting up libmagic-mgc (1:5.45-3+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.24.1) ... Setting up libmagic1t64:arm64 (1:5.45-3+b1) ... Setting up gettext-base (0.23.1-1) ... Setting up m4 (1.4.19-5) ... Setting up file (1:5.45-3+b1) ... Setting up libelf1t64:arm64 (0.192-4) ... Setting up tzdata (2025a-2) ... Current default time zone: 'Etc/UTC' Local time is now: Fri Mar 27 20:52:54 UTC 2026. Universal Time is now: Fri Mar 27 20:52:54 UTC 2026. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up libunistring5:arm64 (1.3-1) ... Setting up autopoint (0.23.1-1) ... Setting up autoconf (2.72-3) ... Setting up libffi8:arm64 (3.4.7-1) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libuchardet0:arm64 (0.0.8-1+b2) ... Setting up netbase (6.4) ... Setting up readline-common (8.2-6) ... Setting up libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Setting up automake (1:1.17-3) ... update-alternatives: using /usr/bin/automake-1.17 to provide /usr/bin/automake (automake) in auto mode Setting up libfile-stripnondeterminism-perl (1.14.1-2) ... Setting up gettext (0.23.1-1) ... Setting up libtool (2.5.4-3) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up libreadline8t64:arm64 (8.2-6) ... Setting up dh-strip-nondeterminism (1.14.1-2) ... Setting up groff-base (1.23.0-7) ... Setting up libpython3.13-stdlib:arm64 (3.13.2-1) ... Setting up libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3.13 (3.13.2-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up python3 (3.13.1-2) ... Setting up python3-zipp (3.21.0-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up man-db (2.13.0-1) ... Not building database; man-db/auto-update is not 'true'. Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-more-itertools (10.6.0-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-typeguard (4.4.1-1) ... Setting up debhelper (13.24.1) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-jaraco.text (4.0.0-1) ... Setting up python3-pkg-resources (75.6.0-1) ... Setting up python3-setuptools (75.6.0-1) ... Setting up dh-python (6.20250108) ... Processing triggers for libc-bin (2.40-7) ... 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 I: Building the package I: user script /srv/workspace/pbuilder/61748/tmp/hooks/A99_set_merged_usr starting Not re-configuring usrmerge for trixie I: user script /srv/workspace/pbuilder/61748/tmp/hooks/A99_set_merged_usr finished hostname: Name or service not known I: Running cd /build/reproducible-path/python3-dmm-0.1.1/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-genchanges -S > ../python3-dmm_0.1.1-1_source.changes dpkg-buildpackage: info: source package python3-dmm dpkg-buildpackage: info: source version 0.1.1-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Jonathan Carter dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --buildsystem=pybuild --with python3 dh_auto_clean -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py clean running clean removing '/build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --buildsystem=pybuild --with python3 dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm copying dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm copying dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm running egg_info creating dmm_highvoltage.egg-info writing dmm_highvoltage.egg-info/PKG-INFO writing dependency_links to dmm_highvoltage.egg-info/dependency_links.txt writing top-level names to dmm_highvoltage.egg-info/top_level.txt writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found anywhere in distribution writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'dmm.modules.aptpkg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptpkg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptpkg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptpkg' to be distributed and are already explicitly excluding 'dmm.modules.aptpkg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.aptsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptsetup' to be distributed and are already explicitly excluding 'dmm.modules.aptsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.cfdisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.cfdisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.cfdisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.cfdisk' to be distributed and are already explicitly excluding 'dmm.modules.cfdisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.checksums' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.checksums' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.checksums' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.checksums' to be distributed and are already explicitly excluding 'dmm.modules.checksums' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dd' to be distributed and are already explicitly excluding 'dmm.modules.dd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.debootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.debootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.debootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.debootstrap' to be distributed and are already explicitly excluding 'dmm.modules.debootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.download' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.download' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.download' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.download' to be distributed and are already explicitly excluding 'dmm.modules.download' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dpkgsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dpkgsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dpkgsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dpkgsetup' to be distributed and are already explicitly excluding 'dmm.modules.dpkgsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.fallocate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.fallocate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.fallocate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.fallocate' to be distributed and are already explicitly excluding 'dmm.modules.fallocate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.grub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.grub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.grub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.grub' to be distributed and are already explicitly excluding 'dmm.modules.grub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.linux' to be distributed and are already explicitly excluding 'dmm.modules.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.livedisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.livedisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.livedisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.livedisk' to be distributed and are already explicitly excluding 'dmm.modules.livedisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.losetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.losetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.losetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.losetup' to be distributed and are already explicitly excluding 'dmm.modules.losetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.lsblk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.lsblk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.lsblk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.lsblk' to be distributed and are already explicitly excluding 'dmm.modules.lsblk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mkfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mkfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mkfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mkfs' to be distributed and are already explicitly excluding 'dmm.modules.mkfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mmdebstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mmdebstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mmdebstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mmdebstrap' to be distributed and are already explicitly excluding 'dmm.modules.mmdebstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mountfs' to be distributed and are already explicitly excluding 'dmm.modules.mountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.networking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.networking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.networking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.networking' to be distributed and are already explicitly excluding 'dmm.modules.networking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.parted' to be distributed and are already explicitly excluding 'dmm.modules.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.readme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.readme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.readme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.readme' to be distributed and are already explicitly excluding 'dmm.modules.readme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.remove' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.remove' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.remove' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.remove' to be distributed and are already explicitly excluding 'dmm.modules.remove' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.reprepro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.reprepro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.reprepro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.reprepro' to be distributed and are already explicitly excluding 'dmm.modules.reprepro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.squashfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.squashfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.squashfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.squashfs' to be distributed and are already explicitly excluding 'dmm.modules.squashfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.umountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.umountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.umountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.umountfs' to be distributed and are already explicitly excluding 'dmm.modules.umountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.users' to be distributed and are already explicitly excluding 'dmm.modules.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.vmsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.vmsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.vmsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.vmsetup' to be distributed and are already explicitly excluding 'dmm.modules.vmsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.writefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.writefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.writefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.writefile' to be distributed and are already explicitly excluding 'dmm.modules.writefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.xorriso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.xorriso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.xorriso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.xorriso' to be distributed and are already explicitly excluding 'dmm.modules.xorriso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums copying dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums copying dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd copying dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd copying dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download copying dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate copying dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub copying dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux copying dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux copying dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk copying dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk copying dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup copying dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup copying dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk copying dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk copying dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs copying dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs copying dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs copying dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs copying dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking copying dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking copying dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted copying dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted copying dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme copying dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme copying dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove copying dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro copying dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs copying dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs copying dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs copying dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users copying dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users copying dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile copying dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso copying dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso copying dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build; python3.13 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s NO TESTS RAN create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python3-dmm-0.1.1/debian/tmp 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 dmm_highvoltage.egg-info/PKG-INFO writing dependency_links to dmm_highvoltage.egg-info/dependency_links.txt writing top-level names to dmm_highvoltage.egg-info/top_level.txt reading manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found anywhere in distribution writing manifest file 'dmm_highvoltage.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'dmm.modules.aptpkg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptpkg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptpkg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptpkg' to be distributed and are already explicitly excluding 'dmm.modules.aptpkg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.aptsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.aptsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.aptsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.aptsetup' to be distributed and are already explicitly excluding 'dmm.modules.aptsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.cfdisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.cfdisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.cfdisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.cfdisk' to be distributed and are already explicitly excluding 'dmm.modules.cfdisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.checksums' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.checksums' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.checksums' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.checksums' to be distributed and are already explicitly excluding 'dmm.modules.checksums' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dd' to be distributed and are already explicitly excluding 'dmm.modules.dd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.debootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.debootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.debootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.debootstrap' to be distributed and are already explicitly excluding 'dmm.modules.debootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.download' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.download' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.download' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.download' to be distributed and are already explicitly excluding 'dmm.modules.download' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.dpkgsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.dpkgsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.dpkgsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.dpkgsetup' to be distributed and are already explicitly excluding 'dmm.modules.dpkgsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.fallocate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.fallocate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.fallocate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.fallocate' to be distributed and are already explicitly excluding 'dmm.modules.fallocate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.grub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.grub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.grub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.grub' to be distributed and are already explicitly excluding 'dmm.modules.grub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.linux' to be distributed and are already explicitly excluding 'dmm.modules.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.livedisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.livedisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.livedisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.livedisk' to be distributed and are already explicitly excluding 'dmm.modules.livedisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.losetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.losetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.losetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.losetup' to be distributed and are already explicitly excluding 'dmm.modules.losetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.lsblk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.lsblk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.lsblk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.lsblk' to be distributed and are already explicitly excluding 'dmm.modules.lsblk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mkfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mkfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mkfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mkfs' to be distributed and are already explicitly excluding 'dmm.modules.mkfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mmdebstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mmdebstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mmdebstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mmdebstrap' to be distributed and are already explicitly excluding 'dmm.modules.mmdebstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.mountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.mountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.mountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.mountfs' to be distributed and are already explicitly excluding 'dmm.modules.mountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.networking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.networking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.networking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.networking' to be distributed and are already explicitly excluding 'dmm.modules.networking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.parted' to be distributed and are already explicitly excluding 'dmm.modules.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.readme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.readme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.readme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.readme' to be distributed and are already explicitly excluding 'dmm.modules.readme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.remove' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.remove' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.remove' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.remove' to be distributed and are already explicitly excluding 'dmm.modules.remove' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.reprepro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.reprepro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.reprepro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.reprepro' to be distributed and are already explicitly excluding 'dmm.modules.reprepro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.squashfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.squashfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.squashfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.squashfs' to be distributed and are already explicitly excluding 'dmm.modules.squashfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.umountfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.umountfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.umountfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.umountfs' to be distributed and are already explicitly excluding 'dmm.modules.umountfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.users' to be distributed and are already explicitly excluding 'dmm.modules.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.vmsetup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.vmsetup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.vmsetup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.vmsetup' to be distributed and are already explicitly excluding 'dmm.modules.vmsetup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.writefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.writefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.writefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.writefile' to be distributed and are already explicitly excluding 'dmm.modules.writefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On 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:212: _Warning: Package 'dmm.modules.xorriso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'dmm.modules.xorriso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'dmm.modules.xorriso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'dmm.modules.xorriso' to be distributed and are already explicitly excluding 'dmm.modules.xorriso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__pycache__ copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__pycache__ creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.13/build/dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso/xorriso.py to xorriso.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/xorriso/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/writefile/writefile.py to writefile.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup/vmsetup.py to vmsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/vmsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users/users.py to users.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/users/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs/umountfs.py to umountfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/umountfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/squashfs/squashfs.py to squashfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/reprepro/reprepro.py to reprepro.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/remove/remove.py to remove.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme/readme.py to readme.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/readme/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted/parted.py to parted.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/parted/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking/networking.py to networking.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/networking/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs/mountfs.py to mountfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mountfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap/mmdebstrap.py to mmdebstrap.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mmdebstrap/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs/mkfs.py to mkfs.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/mkfs/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk/lsblk.py to lsblk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/lsblk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup/losetup.py to losetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/losetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk/livedisk.py to livedisk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/livedisk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux/linux.py to linux.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/linux/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/grub/grub.py to grub.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/fallocate/fallocate.py to fallocate.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup/dpkgsetup.py to dpkgsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dpkgsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/download/download.py to download.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap/debootstrap.py to debootstrap.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/debootstrap/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd/dd.py to dd.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/dd/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums/checksums.py to checksums.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/checksums/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk/cfdisk.py to cfdisk.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/cfdisk/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup/aptsetup.py to aptsetup.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptsetup/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg/aptpkg.py to aptpkg.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/modules/aptpkg/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm/dmm.py to dmm.cpython-313.pyc running install_egg_info Copying dmm_highvoltage.egg-info to /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.13/dist-packages/dmm_highvoltage-0.0.2.egg-info Skipping SOURCES.txt running install_scripts dh_install -O--buildsystem=pybuild dh_installdocs -O--buildsystem=pybuild dh_installchangelogs -O--buildsystem=pybuild dh_python3 -O--buildsystem=pybuild dh_installsystemduser -O--buildsystem=pybuild dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild dh_compress -O--buildsystem=pybuild dh_fixperms -O--buildsystem=pybuild dh_missing -O--buildsystem=pybuild dh_installdeb -O--buildsystem=pybuild dh_gencontrol -O--buildsystem=pybuild dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-dmm' in '../python3-dmm_0.1.1-1_all.deb'. dpkg-deb: building package 'dmm-utils' in '../dmm-utils_0.1.1-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python3-dmm_0.1.1-1_arm64.buildinfo dpkg-genchanges --build=binary -O../python3-dmm_0.1.1-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: user script /srv/workspace/pbuilder/61748/tmp/hooks/B01_cleanup starting I: user script /srv/workspace/pbuilder/61748/tmp/hooks/B01_cleanup finished 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/61748 and its subdirectories I: Current time: Sat Mar 28 10:53:17 +14 2026 I: pbuilder-time-stamp: 1774644797 + false + set +x Fri Mar 27 20:53:17 UTC 2026 I: Signing ./b2/python3-dmm_0.1.1-1_arm64.buildinfo as python3-dmm_0.1.1-1_arm64.buildinfo.asc Fri Mar 27 20:53:17 UTC 2026 I: Signed ./b2/python3-dmm_0.1.1-1_arm64.buildinfo as ./b2/python3-dmm_0.1.1-1_arm64.buildinfo.asc Fri Mar 27 20:53:17 UTC 2026 - build #2 for python3-dmm/trixie/arm64 on codethink03-arm64 done. Starting cleanup. All cleanup done. Fri Mar 27 20:53:17 UTC 2026 - reproducible_build.sh stopped running as /tmp/jenkins-script-hiWWaeoe, removing. /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb: total 196 drwxr-xr-x 2 jenkins jenkins 4096 Feb 22 14:29 b1 drwxr-xr-x 2 jenkins jenkins 4096 Feb 22 14:30 b2 -rw-r--r-- 1 jenkins jenkins 2027 Feb 8 2023 python3-dmm_0.1.1-1.dsc -rw------- 1 jenkins jenkins 182302 Feb 22 14:29 rbuildlog.5IWN6DX /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b1: total 668 -rw-r--r-- 1 jenkins jenkins 178840 Feb 22 14:29 build.log -rw-r--r-- 1 jenkins jenkins 216984 Feb 22 14:29 dmm-utils_0.1.1-1_all.deb -rw-r--r-- 1 jenkins jenkins 2244 Feb 22 14:29 python3-dmm_0.1.1-1.debian.tar.xz -rw-r--r-- 1 jenkins jenkins 2027 Feb 22 14:29 python3-dmm_0.1.1-1.dsc -rw-r--r-- 1 jenkins jenkins 12224 Feb 22 14:29 python3-dmm_0.1.1-1_all.deb -rw-r--r-- 1 jenkins jenkins 5687 Feb 22 14:29 python3-dmm_0.1.1-1_arm64.buildinfo -rw-r--r-- 1 jenkins jenkins 6569 Feb 22 14:29 python3-dmm_0.1.1-1_arm64.buildinfo.asc -rw-r--r-- 1 jenkins jenkins 1424 Feb 22 14:29 python3-dmm_0.1.1-1_arm64.changes -rw-r--r-- 1 jenkins jenkins 1551 Feb 22 14:29 python3-dmm_0.1.1-1_source.changes -rw-r--r-- 1 jenkins jenkins 227377 Feb 22 14:29 python3-dmm_0.1.1.orig.tar.gz /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2: total 660 -rw-r--r-- 1 jenkins jenkins 180763 Feb 22 14:30 build.log -rw-r--r-- 1 jenkins jenkins 216984 Feb 22 14:30 dmm-utils_0.1.1-1_all.deb -rw-r--r-- 1 jenkins jenkins 2244 Feb 22 14:30 python3-dmm_0.1.1-1.debian.tar.xz -rw-r--r-- 1 jenkins jenkins 2027 Feb 22 14:30 python3-dmm_0.1.1-1.dsc -rw-r--r-- 1 jenkins jenkins 12224 Feb 22 14:30 python3-dmm_0.1.1-1_all.deb -rw-r--r-- 1 jenkins jenkins 5687 Feb 22 14:30 python3-dmm_0.1.1-1_arm64.buildinfo -rw-r--r-- 1 jenkins jenkins 6569 Feb 22 14:30 python3-dmm_0.1.1-1_arm64.buildinfo.asc -rw-r--r-- 1 jenkins jenkins 1424 Feb 22 14:30 python3-dmm_0.1.1-1_arm64.changes -rw-r--r-- 1 jenkins jenkins 1551 Feb 22 14:30 python3-dmm_0.1.1-1_source.changes -rw-r--r-- 1 jenkins jenkins 227377 Feb 22 14:30 python3-dmm_0.1.1.orig.tar.gz Sat Feb 22 14:30:18 UTC 2025 I: Deleting $TMPDIR on codethink03-arm64.debian.net. Sat Feb 22 14:30:19 UTC 2025 I: python3-dmm_0.1.1-1_arm64.changes: Format: 1.8 Date: Wed, 08 Feb 2023 09:28:02 +0200 Source: python3-dmm Binary: dmm-utils python3-dmm Architecture: all Version: 0.1.1-1 Distribution: unstable Urgency: medium Maintainer: Jonathan Carter Changed-By: Jonathan Carter Description: dmm-utils - Tools for making use of python3-dmm python3-dmm - distribution management modules/toolkit Changes: python3-dmm (0.1.1-1) unstable; urgency=medium . * New upstream release * Add dependencies: python3-yaml, python3-loguru * Update copyright years * Declare standards version 4.6.2 Checksums-Sha1: 35b54f583a84fa7c3a8545a1b1cfc8c1b7a7662c 216984 dmm-utils_0.1.1-1_all.deb 800e1d81a22cc21a8645cf8bd7eb4d31b3f14e5b 12224 python3-dmm_0.1.1-1_all.deb 5d980627124a5320c9466f6e05515f8bc44f1078 5687 python3-dmm_0.1.1-1_arm64.buildinfo Checksums-Sha256: e3b142f63fd38f3a42102be43977f0922faa7b7ac6cfbf127d1b23bd4d974201 216984 dmm-utils_0.1.1-1_all.deb f4d68811bd44477bba7891a1c300ab6d618b296636ec30bd733f95947cc3f067 12224 python3-dmm_0.1.1-1_all.deb 10d5726fe24cc0af1b3407e91e5c29df21f6a2c222cf6ac400422d451ddf5242 5687 python3-dmm_0.1.1-1_arm64.buildinfo Files: eb4a0d9dfd88ec9ebe7801b1303db4b8 216984 python optional dmm-utils_0.1.1-1_all.deb 8a530127c2bf6b674712201c09bc200f 12224 python optional python3-dmm_0.1.1-1_all.deb 9e7aaf5047dcc36b05b9af199cef7e92 5687 python optional python3-dmm_0.1.1-1_arm64.buildinfo removed '/var/lib/jenkins/userContent/reproducible/debian/rbuild/trixie/arm64/python3-dmm_0.1.1-1.rbuild.log' removed '/var/lib/jenkins/userContent/reproducible/debian/rbuild/trixie/arm64/python3-dmm_0.1.1-1.rbuild.log.gz' removed '/var/lib/jenkins/userContent/reproducible/debian/logs/trixie/arm64/python3-dmm_0.1.1-1.build1.log.gz' removed '/var/lib/jenkins/userContent/reproducible/debian/logs/trixie/arm64/python3-dmm_0.1.1-1.build2.log.gz' removed '/var/lib/jenkins/userContent/reproducible/debian/buildinfo/trixie/arm64/python3-dmm_0.1.1-1_arm64.buildinfo' removed '/var/lib/jenkins/userContent/reproducible/debian/logdiffs/trixie/arm64/python3-dmm_0.1.1-1.diff.gz' Diff of the two buildlogs: -- --- b1/build.log 2025-02-22 14:29:19.507930026 +0000 +++ b2/build.log 2025-02-22 14:30:18.625242936 +0000 @@ -1,6 +1,6 @@ I: pbuilder: network access will be disabled during build -I: Current time: Sat Feb 22 02:28:42 -12 2025 -I: pbuilder-time-stamp: 1740234522 +I: Current time: Sat Mar 28 10:52:22 +14 2026 +I: pbuilder-time-stamp: 1774644742 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/trixie-reproducible-base.tgz] I: copying local configuration @@ -22,52 +22,84 @@ dpkg-source: info: unpacking python3-dmm_0.1.1-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps -I: user script /srv/workspace/pbuilder/3301095/tmp/hooks/D02_print_environment starting +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/D01_modify_environment starting +debug: Running on codethink03-arm64. +I: Changing host+domainname to test build reproducibility +I: Adding a custom variable just for the fun of it... +I: Changing /bin/sh to bash +'/bin/sh' -> '/bin/bash' +lrwxrwxrwx 1 root root 9 Mar 27 20:52 /bin/sh -> /bin/bash +I: Setting pbuilder2's login shell to /bin/bash +I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/D01_modify_environment finished +I: user script /srv/workspace/pbuilder/61748/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' + BASH=/bin/sh + BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:globskipdots:hostcomplete:interactive_comments:patsub_replacement:progcomp:promptvars:sourcepath + BASH_ALIASES=() + BASH_ARGC=() + BASH_ARGV=() + BASH_CMDS=() + BASH_LINENO=([0]="12" [1]="0") + BASH_LOADABLES_PATH=/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib/bash:. + BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") + BASH_VERSINFO=([0]="5" [1]="2" [2]="37" [3]="1" [4]="release" [5]="aarch64-unknown-linux-gnu") + BASH_VERSION='5.2.37(1)-release' + BUILDDIR=/build/reproducible-path + BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' + BUILDUSERNAME=pbuilder2 + BUILD_ARCH=arm64 + DEBIAN_FRONTEND=noninteractive DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' - DISTRIBUTION='trixie' - HOME='/root' - HOST_ARCH='arm64' + DIRSTACK=() + DISTRIBUTION=trixie + EUID=0 + FUNCNAME=([0]="Echo" [1]="main") + GROUPS=() + HOME=/root + HOSTNAME=i-capture-the-hostname + HOSTTYPE=aarch64 + HOST_ARCH=arm64 IFS=' ' - INVOCATION_ID='b2363ea5bbf24a6dab6e738328e0bf29' - 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='3301095' - PS1='# ' - PS2='> ' + INVOCATION_ID=96fb3e1ed60944508b2d9c9a24da5086 + LANG=C + LANGUAGE=nl_BE:nl + LC_ALL=C + MACHTYPE=aarch64-unknown-linux-gnu + MAIL=/var/mail/root + OPTERR=1 + OPTIND=1 + OSTYPE=linux-gnu + PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path + PBCURRENTCOMMANDLINEOPERATION=build + PBUILDER_OPERATION=build + PBUILDER_PKGDATADIR=/usr/share/pbuilder + PBUILDER_PKGLIBDIR=/usr/lib/pbuilder + PBUILDER_SYSCONFDIR=/etc + PIPESTATUS=([0]="0") + POSIXLY_CORRECT=y + PPID=61748 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.yP0UuGAb/pbuilderrc_oxP6 --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.yP0UuGAb/b1 --logfile b1/build.log python3-dmm_0.1.1-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' + PWD=/ + SHELL=/bin/bash + SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix + SHLVL=3 + SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/pbuilderrc_24aV --distribution trixie --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/trixie-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2 --logfile b2/build.log python3-dmm_0.1.1-1.dsc' + SUDO_GID=109 + SUDO_UID=104 + SUDO_USER=jenkins + TERM=unknown + TZ=/usr/share/zoneinfo/Etc/GMT-14 + UID=0 + USER=root + _='I: set' + http_proxy=http://192.168.101.4:3128 I: uname -a - Linux codethink04-arm64 6.1.0-31-cloud-arm64 #1 SMP Debian 6.1.128-1 (2025-02-07) aarch64 GNU/Linux + Linux i-capture-the-hostname 6.1.0-31-cloud-arm64 #1 SMP Debian 6.1.128-1 (2025-02-07) aarch64 GNU/Linux I: ls -l /bin - lrwxrwxrwx 1 root root 7 Nov 22 14:40 /bin -> usr/bin -I: user script /srv/workspace/pbuilder/3301095/tmp/hooks/D02_print_environment finished + lrwxrwxrwx 1 root root 7 Nov 22 2024 /bin -> usr/bin +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy @@ -80,7 +112,7 @@ Depends: debhelper-compat (= 13), dh-python, python3-setuptools, python3 dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. -(Reading database ... 19972 files and directories currently installed.) +(Reading database ... 19922 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: @@ -165,10 +197,10 @@ Get: 54 http://deb.debian.org/debian trixie/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 55 http://deb.debian.org/debian trixie/main arm64 python3-setuptools all 75.6.0-1 [720 kB] Get: 56 http://deb.debian.org/debian trixie/main arm64 dh-python all 6.20250108 [113 kB] -Fetched 27.6 MB in 0s (151 MB/s) +Fetched 27.6 MB in 0s (106 MB/s) Preconfiguring packages ... Selecting previously unselected package libpython3.13-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 ... 19972 files and directories currently installed.) +(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 ... 19922 files and directories currently installed.) Preparing to unpack .../libpython3.13-minimal_3.13.2-1_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.2-1) ... Selecting previously unselected package libexpat1:arm64. @@ -181,7 +213,7 @@ Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.13-minimal (3.13.2-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 ... 20306 files and directories currently installed.) +(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 ... 20256 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.13.1-2_arm64.deb ... Unpacking python3-minimal (3.13.1-2) ... Selecting previously unselected package media-types. @@ -217,7 +249,7 @@ Unpacking libpython3-stdlib:arm64 (3.13.1-2) ... Setting up python3-minimal (3.13.1-2) ... 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 ... 21316 files and directories currently installed.) +(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 ... 21266 files and directories currently installed.) Preparing to unpack .../00-python3_3.13.1-2_arm64.deb ... Unpacking python3 (3.13.1-2) ... Selecting previously unselected package sensible-utils. @@ -361,8 +393,8 @@ Setting up tzdata (2025a-2) ... Current default time zone: 'Etc/UTC' -Local time is now: Sat Feb 22 14:29:03 UTC 2025. -Universal Time is now: Sat Feb 22 14:29:03 UTC 2025. +Local time is now: Fri Mar 27 20:52:54 UTC 2026. +Universal Time is now: Fri Mar 27 20:52:54 UTC 2026. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... @@ -416,7 +448,11 @@ Building tag database... -> Finished parsing the build-deps I: Building the package -I: Running cd /build/reproducible-path/python3-dmm-0.1.1/ && 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 > ../python3-dmm_0.1.1-1_source.changes +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/A99_set_merged_usr starting +Not re-configuring usrmerge for trixie +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/A99_set_merged_usr finished +hostname: Name or service not known +I: Running cd /build/reproducible-path/python3-dmm-0.1.1/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-genchanges -S > ../python3-dmm_0.1.1-1_source.changes dpkg-buildpackage: info: source package python3-dmm dpkg-buildpackage: info: source version 0.1.1-1 dpkg-buildpackage: info: source distribution unstable @@ -3030,12 +3066,14 @@ dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/B01_cleanup starting +I: user script /srv/workspace/pbuilder/61748/tmp/hooks/B01_cleanup finished 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/3301095 and its subdirectories -I: Current time: Sat Feb 22 02:29:18 -12 2025 -I: pbuilder-time-stamp: 1740234558 +I: removing directory /srv/workspace/pbuilder/61748 and its subdirectories +I: Current time: Sat Mar 28 10:53:17 +14 2026 +I: pbuilder-time-stamp: 1774644797 Compressing the 2nd log... /var/lib/jenkins/userContent/reproducible/debian/logdiffs/trixie/arm64/python3-dmm_0.1.1-1.diff: 74.7% -- replaced with /var/lib/jenkins/userContent/reproducible/debian/logdiffs/trixie/arm64/python3-dmm_0.1.1-1.diff.gz b2/build.log: 93.3% -- replaced with stdout Compressing the 1st log... b1/build.log: 93.7% -- replaced with stdout Sat Feb 22 14:30:20 UTC 2025 I: diffoscope 289 will be used to compare the two builds: ++ date -u +%s + DIFFOSCOPE_STAMP=/var/log/reproducible-builds/diffoscope_stamp_python3-dmm_trixie_arm64_1740234620 + touch /var/log/reproducible-builds/diffoscope_stamp_python3-dmm_trixie_arm64_1740234620 + RESULT=0 + systemd-run '--description=diffoscope on python3-dmm/0.1.1-1 in trixie/arm64' --slice=rb-build-diffoscope.slice -u rb-diffoscope-arm64_11-85165 '--property=SuccessExitStatus=1 124' --user --send-sighup --pipe --wait -E TMPDIR timeout 155m nice schroot --directory /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb --run-session -c jenkins-reproducible-trixie-diffoscope-3bdffe82-49dd-4dde-8890-92c1123723f8 -- sh -c 'export TMPDIR=/srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/dbd-tmp-5QcAI95 ; timeout 150m diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/python3-dmm_0.1.1-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/python3-dmm_0.1.1-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/python3-dmm_0.1.1-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b1/python3-dmm_0.1.1-1_arm64.changes /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2/python3-dmm_0.1.1-1_arm64.changes' + false + set +x Running as unit: rb-diffoscope-arm64_11-85165.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/python3-dmm_0.1.1-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/python3-dmm_0.1.1-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/python3-dmm_0.1.1-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b1/python3-dmm_0.1.1-1_arm64.changes /srv/reproducible-results/rbuild-debian/r-b-build.yP0UuGAb/b2/python3-dmm_0.1.1-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 diffoscope.comparators.binary.FilesystemFile ## main (total time: 0.003s) 0.003s 2 calls outputs 0.000s 1 call cleanup Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 226ms CPU time consumed: 228ms _ _ _____ _ _ __ _ _| |_| |__ ___ _ __ |___ / __| |_ __ ___ _ __ ___ | '_ \| | | | __| '_ \ / _ \| '_ \ |_ \ _____ / _` | '_ ` _ \| '_ ` _ \ | |_) | |_| | |_| | | | (_) | | | |___) |_____| (_| | | | | | | | | | | | | .__/ \__, |\__|_| |_|\___/|_| |_|____/ \__,_|_| |_| |_|_| |_| |_| |_| |___/ Sat Feb 22 14:30:21 UTC 2025 I: diffoscope 289 found no differences in the changes files, and a .buildinfo file also exists. Sat Feb 22 14:30:21 UTC 2025 I: python3-dmm from trixie built successfully and reproducibly on arm64. INSERT 0 1 INSERT 0 1 DELETE 1 [2025-02-22 14:30:22] INFO: Starting at 2025-02-22 14:30:22.407490 [2025-02-22 14:30:22] INFO: Generating the pages of 1 package(s) [2025-02-22 14:30:22] CRITICAL: https://tests.reproducible-builds.org/debian/trixie/arm64/python3-dmm didn't produce a buildlog, even though it has been built. [2025-02-22 14:30:22] INFO: Finished at 2025-02-22 14:30:22.757623, took: 0:00:00.350141 Sat Feb 22 14:30:22 UTC 2025 - successfully updated the database and updated https://tests.reproducible-builds.org/debian/rb-pkg/trixie/arm64/python3-dmm.html Sat Feb 22 14:30:22 UTC 2025 I: Submitting .buildinfo files to external archives: Sat Feb 22 14:30:22 UTC 2025 I: Submitting 8.0K b1/python3-dmm_0.1.1-1_arm64.buildinfo.asc https://buildinfo.debian.net/5d980627124a5320c9466f6e05515f8bc44f1078/python3-dmm_0.1.1-1_all Sat Feb 22 14:30:23 UTC 2025 I: Submitting 8.0K b2/python3-dmm_0.1.1-1_arm64.buildinfo.asc https://buildinfo.debian.net/19ec767b7d7da9c70618390eee173c18648e4d74/python3-dmm_0.1.1-1_all Sat Feb 22 14:30:24 UTC 2025 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Sat Feb 22 14:30:24 UTC 2025 I: Done submitting .buildinfo files. Sat Feb 22 14:30:24 UTC 2025 I: Removing signed python3-dmm_0.1.1-1_arm64.buildinfo.asc files: removed './b1/python3-dmm_0.1.1-1_arm64.buildinfo.asc' removed './b2/python3-dmm_0.1.1-1_arm64.buildinfo.asc' 1740234624 arm64 trixie python3-dmm Starting cleanup. /var/lib/jenkins/userContent/reproducible/debian/rbuild/trixie/arm64/python3-dmm_0.1.1-1.rbuild.log: 92.3% -- replaced with /var/lib/jenkins/userContent/reproducible/debian/rbuild/trixie/arm64/python3-dmm_0.1.1-1.rbuild.log.gz [2025-02-22 14:30:24] INFO: Starting at 2025-02-22 14:30:24.978721 [2025-02-22 14:30:25] INFO: Generating the pages of 1 package(s) [2025-02-22 14:30:25] INFO: Finished at 2025-02-22 14:30:25.232631, took: 0:00:00.253918 All cleanup done. Sat Feb 22 14:30:25 UTC 2025 - total duration: 0h 2m 6s. Sat Feb 22 14:30:25 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-9g5H09sy, removing. Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 2min 9.842s CPU time consumed: 6.753s