Sun Apr 7 08:55:04 UTC 2024 I: starting to build python3-dmm/trixie/i386 on jenkins on '2024-04-07 08:54' Sun Apr 7 08:55:04 UTC 2024 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/i386_6/19227/console.log Sun Apr 7 08:55:04 UTC 2024 I: Downloading source for trixie/python3-dmm=0.1.1-1 --2024-04-07 08:55:05-- http://deb.debian.org/debian/pool/main/p/python3-dmm/python3-dmm_0.1.1-1.dsc Connecting to 78.137.99.97: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% 12.0M=0s 2024-04-07 08:55:05 (12.0 MB/s) - ‘python3-dmm_0.1.1-1.dsc’ saved [2027/2027] Sun Apr 7 08:55:05 UTC 2024 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----- Sun Apr 7 08:55:05 UTC 2024 I: Checking whether the package is not for us Sun Apr 7 08:55:05 UTC 2024 I: Starting 1st build on remote node ionos6-i386.debian.net. Sun Apr 7 08:55:05 UTC 2024 I: Preparing to do remote build '1' on ionos6-i386.debian.net. Sun Apr 7 08:55:37 UTC 2024 I: Deleting $TMPDIR on ionos6-i386.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Sat May 10 03:18:06 -12 2025 I: pbuilder-time-stamp: 1746890286 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: using eatmydata during job 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 gpgv: Signature made Wed Feb 8 07:30:10 2023 gpgv: using RSA key C7203C0A920670BF94F00BB1B01D1A72AC8DC9A1 gpgv: issuer "jcc@debian.org" gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./python3-dmm_0.1.1-1.dsc: no acceptable signature found 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/109132/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='i386' DEBIAN_FRONTEND='noninteractive' DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=22 ' DISTRIBUTION='trixie' HOME='/root' HOST_ARCH='i386' IFS=' ' INVOCATION_ID='701a446439494aa3a335c40316a87684' LANG='C' LANGUAGE='en_US:en' LC_ALL='C' LD_LIBRARY_PATH='/usr/lib/libeatmydata' LD_PRELOAD='libeatmydata.so' 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='109132' 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.AKOvzu8n/pbuilderrc_TVRv --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.AKOvzu8n/b1 --logfile b1/build.log python3-dmm_0.1.1-1.dsc' SUDO_GID='112' SUDO_UID='107' SUDO_USER='jenkins' TERM='unknown' TZ='/usr/share/zoneinfo/Etc/GMT+12' USER='root' _='/usr/bin/systemd-run' http_proxy='http://85.184.249.68:3128' I: uname -a Linux ionos6-i386 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 May 8 17:46 /bin -> usr/bin I: user script /srv/workspace/pbuilder/109132/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: i386 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 ... 19876 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} libelf1{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libicu72{a} libmagic-mgc{a} libmagic1{a} libpipeline1{a} libpython3-stdlib{a} libpython3.11-minimal{a} libpython3.11-stdlib{a} libreadline8{a} libsub-override-perl{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} po-debconf{a} python3{a} python3-distutils{a} python3-lib2to3{a} python3-minimal{a} python3-pkg-resources{a} python3-setuptools{a} python3.11{a} python3.11-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, 48 newly installed, 0 to remove and 0 not upgraded. Need to get 26.3 MB of archives. After unpacking 102 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian trixie/main i386 libpython3.11-minimal i386 3.11.8-1 [817 kB] Get: 2 http://deb.debian.org/debian trixie/main i386 libexpat1 i386 2.5.0-2+b2 [104 kB] Get: 3 http://deb.debian.org/debian trixie/main i386 python3.11-minimal i386 3.11.8-1 [2087 kB] Get: 4 http://deb.debian.org/debian trixie/main i386 python3-minimal i386 3.11.6-1 [26.2 kB] Get: 5 http://deb.debian.org/debian trixie/main i386 media-types all 10.1.0 [26.9 kB] Get: 6 http://deb.debian.org/debian trixie/main i386 netbase all 6.4 [12.8 kB] Get: 7 http://deb.debian.org/debian trixie/main i386 tzdata all 2024a-1 [255 kB] Get: 8 http://deb.debian.org/debian trixie/main i386 readline-common all 8.2-3 [69.1 kB] Get: 9 http://deb.debian.org/debian trixie/main i386 libreadline8 i386 8.2-3+b1 [171 kB] Get: 10 http://deb.debian.org/debian trixie/main i386 libpython3.11-stdlib i386 3.11.8-1 [1821 kB] Get: 11 http://deb.debian.org/debian trixie/main i386 python3.11 i386 3.11.8-1 [597 kB] Get: 12 http://deb.debian.org/debian trixie/main i386 libpython3-stdlib i386 3.11.6-1 [9224 B] Get: 13 http://deb.debian.org/debian trixie/main i386 python3 i386 3.11.6-1 [26.2 kB] Get: 14 http://deb.debian.org/debian trixie/main i386 sensible-utils all 0.0.22 [22.4 kB] Get: 15 http://deb.debian.org/debian trixie/main i386 libmagic-mgc i386 1:5.45-2+b1 [314 kB] Get: 16 http://deb.debian.org/debian trixie/main i386 libmagic1 i386 1:5.45-2+b1 [114 kB] Get: 17 http://deb.debian.org/debian trixie/main i386 file i386 1:5.45-2+b1 [43.0 kB] Get: 18 http://deb.debian.org/debian trixie/main i386 gettext-base i386 0.21-14+b1 [162 kB] Get: 19 http://deb.debian.org/debian trixie/main i386 libuchardet0 i386 0.0.8-1+b1 [69.1 kB] Get: 20 http://deb.debian.org/debian trixie/main i386 groff-base i386 1.23.0-3 [1195 kB] Get: 21 http://deb.debian.org/debian trixie/main i386 bsdextrautils i386 2.39.3-6 [93.3 kB] Get: 22 http://deb.debian.org/debian trixie/main i386 libpipeline1 i386 1.5.7-2 [39.7 kB] Get: 23 http://deb.debian.org/debian trixie/main i386 man-db i386 2.12.0-3 [1413 kB] Get: 24 http://deb.debian.org/debian trixie/main i386 m4 i386 1.4.19-4 [293 kB] Get: 25 http://deb.debian.org/debian trixie/main i386 autoconf all 2.71-3 [332 kB] Get: 26 http://deb.debian.org/debian trixie/main i386 autotools-dev all 20220109.1 [51.6 kB] Get: 27 http://deb.debian.org/debian trixie/main i386 automake all 1:1.16.5-1.3 [823 kB] Get: 28 http://deb.debian.org/debian trixie/main i386 autopoint all 0.21-14 [496 kB] Get: 29 http://deb.debian.org/debian trixie/main i386 libdebhelper-perl all 13.15.3 [88.0 kB] Get: 30 http://deb.debian.org/debian trixie/main i386 libtool all 2.4.7-7 [517 kB] Get: 31 http://deb.debian.org/debian trixie/main i386 dh-autoreconf all 20 [17.1 kB] Get: 32 http://deb.debian.org/debian trixie/main i386 libarchive-zip-perl all 1.68-1 [104 kB] Get: 33 http://deb.debian.org/debian trixie/main i386 libsub-override-perl all 0.10-1 [10.6 kB] Get: 34 http://deb.debian.org/debian trixie/main i386 libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB] Get: 35 http://deb.debian.org/debian trixie/main i386 dh-strip-nondeterminism all 1.13.1-1 [8620 B] Get: 36 http://deb.debian.org/debian trixie/main i386 libelf1 i386 0.190-1+b1 [182 kB] Get: 37 http://deb.debian.org/debian trixie/main i386 dwz i386 0.15-1 [118 kB] Get: 38 http://deb.debian.org/debian trixie/main i386 libicu72 i386 72.1-4+b1 [9549 kB] Get: 39 http://deb.debian.org/debian trixie/main i386 libxml2 i386 2.9.14+dfsg-1.3+b2 [727 kB] Get: 40 http://deb.debian.org/debian trixie/main i386 gettext i386 0.21-14+b1 [1311 kB] Get: 41 http://deb.debian.org/debian trixie/main i386 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 42 http://deb.debian.org/debian trixie/main i386 po-debconf all 1.0.21+nmu1 [248 kB] Get: 43 http://deb.debian.org/debian trixie/main i386 debhelper all 13.15.3 [901 kB] Get: 44 http://deb.debian.org/debian trixie/main i386 python3-pkg-resources all 68.1.2-2 [241 kB] Get: 45 http://deb.debian.org/debian trixie/main i386 python3-lib2to3 all 3.11.5-1 [77.5 kB] Get: 46 http://deb.debian.org/debian trixie/main i386 python3-distutils all 3.11.5-1 [131 kB] Get: 47 http://deb.debian.org/debian trixie/main i386 python3-setuptools all 68.1.2-2 [468 kB] Get: 48 http://deb.debian.org/debian trixie/main i386 dh-python all 6.20240401 [107 kB] Fetched 26.3 MB in 0s (92.6 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libpython3.11-minimal:i386. (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 ... 19876 files and directories currently installed.) Preparing to unpack .../libpython3.11-minimal_3.11.8-1_i386.deb ... Unpacking libpython3.11-minimal:i386 (3.11.8-1) ... Selecting previously unselected package libexpat1:i386. Preparing to unpack .../libexpat1_2.5.0-2+b2_i386.deb ... Unpacking libexpat1:i386 (2.5.0-2+b2) ... Selecting previously unselected package python3.11-minimal. Preparing to unpack .../python3.11-minimal_3.11.8-1_i386.deb ... Unpacking python3.11-minimal (3.11.8-1) ... Setting up libpython3.11-minimal:i386 (3.11.8-1) ... Setting up libexpat1:i386 (2.5.0-2+b2) ... Setting up python3.11-minimal (3.11.8-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 ... 20193 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.11.6-1_i386.deb ... Unpacking python3-minimal (3.11.6-1) ... Selecting previously unselected package media-types. Preparing to unpack .../1-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../2-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package tzdata. Preparing to unpack .../3-tzdata_2024a-1_all.deb ... Unpacking tzdata (2024a-1) ... Selecting previously unselected package readline-common. Preparing to unpack .../4-readline-common_8.2-3_all.deb ... Unpacking readline-common (8.2-3) ... Selecting previously unselected package libreadline8:i386. Preparing to unpack .../5-libreadline8_8.2-3+b1_i386.deb ... Unpacking libreadline8:i386 (8.2-3+b1) ... Selecting previously unselected package libpython3.11-stdlib:i386. Preparing to unpack .../6-libpython3.11-stdlib_3.11.8-1_i386.deb ... Unpacking libpython3.11-stdlib:i386 (3.11.8-1) ... Selecting previously unselected package python3.11. Preparing to unpack .../7-python3.11_3.11.8-1_i386.deb ... Unpacking python3.11 (3.11.8-1) ... Selecting previously unselected package libpython3-stdlib:i386. Preparing to unpack .../8-libpython3-stdlib_3.11.6-1_i386.deb ... Unpacking libpython3-stdlib:i386 (3.11.6-1) ... Setting up python3-minimal (3.11.6-1) ... Selecting previously unselected package python3. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 21181 files and directories currently installed.) Preparing to unpack .../00-python3_3.11.6-1_i386.deb ... Unpacking python3 (3.11.6-1) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../01-sensible-utils_0.0.22_all.deb ... Unpacking sensible-utils (0.0.22) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../02-libmagic-mgc_1%3a5.45-2+b1_i386.deb ... Unpacking libmagic-mgc (1:5.45-2+b1) ... Selecting previously unselected package libmagic1:i386. Preparing to unpack .../03-libmagic1_1%3a5.45-2+b1_i386.deb ... Unpacking libmagic1:i386 (1:5.45-2+b1) ... Selecting previously unselected package file. Preparing to unpack .../04-file_1%3a5.45-2+b1_i386.deb ... Unpacking file (1:5.45-2+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../05-gettext-base_0.21-14+b1_i386.deb ... Unpacking gettext-base (0.21-14+b1) ... Selecting previously unselected package libuchardet0:i386. Preparing to unpack .../06-libuchardet0_0.0.8-1+b1_i386.deb ... Unpacking libuchardet0:i386 (0.0.8-1+b1) ... Selecting previously unselected package groff-base. Preparing to unpack .../07-groff-base_1.23.0-3_i386.deb ... Unpacking groff-base (1.23.0-3) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../08-bsdextrautils_2.39.3-6_i386.deb ... Unpacking bsdextrautils (2.39.3-6) ... Selecting previously unselected package libpipeline1:i386. Preparing to unpack .../09-libpipeline1_1.5.7-2_i386.deb ... Unpacking libpipeline1:i386 (1.5.7-2) ... Selecting previously unselected package man-db. Preparing to unpack .../10-man-db_2.12.0-3_i386.deb ... Unpacking man-db (2.12.0-3) ... Selecting previously unselected package m4. Preparing to unpack .../11-m4_1.4.19-4_i386.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../12-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-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.16.5-1.3_all.deb ... Unpacking automake (1:1.16.5-1.3) ... Selecting previously unselected package autopoint. Preparing to unpack .../15-autopoint_0.21-14_all.deb ... Unpacking autopoint (0.21-14) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../16-libdebhelper-perl_13.15.3_all.deb ... Unpacking libdebhelper-perl (13.15.3) ... Selecting previously unselected package libtool. Preparing to unpack .../17-libtool_2.4.7-7_all.deb ... Unpacking libtool (2.4.7-7) ... 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 libsub-override-perl. Preparing to unpack .../20-libsub-override-perl_0.10-1_all.deb ... Unpacking libsub-override-perl (0.10-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../21-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../22-dh-strip-nondeterminism_1.13.1-1_all.deb ... Unpacking dh-strip-nondeterminism (1.13.1-1) ... Selecting previously unselected package libelf1:i386. Preparing to unpack .../23-libelf1_0.190-1+b1_i386.deb ... Unpacking libelf1:i386 (0.190-1+b1) ... Selecting previously unselected package dwz. Preparing to unpack .../24-dwz_0.15-1_i386.deb ... Unpacking dwz (0.15-1) ... Selecting previously unselected package libicu72:i386. Preparing to unpack .../25-libicu72_72.1-4+b1_i386.deb ... Unpacking libicu72:i386 (72.1-4+b1) ... Selecting previously unselected package libxml2:i386. Preparing to unpack .../26-libxml2_2.9.14+dfsg-1.3+b2_i386.deb ... Unpacking libxml2:i386 (2.9.14+dfsg-1.3+b2) ... Selecting previously unselected package gettext. Preparing to unpack .../27-gettext_0.21-14+b1_i386.deb ... Unpacking gettext (0.21-14+b1) ... 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.15.3_all.deb ... Unpacking debhelper (13.15.3) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../31-python3-pkg-resources_68.1.2-2_all.deb ... Unpacking python3-pkg-resources (68.1.2-2) ... Selecting previously unselected package python3-lib2to3. Preparing to unpack .../32-python3-lib2to3_3.11.5-1_all.deb ... Unpacking python3-lib2to3 (3.11.5-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../33-python3-distutils_3.11.5-1_all.deb ... Unpacking python3-distutils (3.11.5-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../34-python3-setuptools_68.1.2-2_all.deb ... Unpacking python3-setuptools (68.1.2-2) ... Selecting previously unselected package dh-python. Preparing to unpack .../35-dh-python_6.20240401_all.deb ... Unpacking dh-python (6.20240401) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:i386 (1.5.7-2) ... Setting up libicu72:i386 (72.1-4+b1) ... Setting up bsdextrautils (2.39.3-6) ... Setting up libmagic-mgc (1:5.45-2+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.15.3) ... Setting up libmagic1:i386 (1:5.45-2+b1) ... Setting up gettext-base (0.21-14+b1) ... Setting up m4 (1.4.19-4) ... Setting up file (1:5.45-2+b1) ... Setting up tzdata (2024a-1) ... Current default time zone: 'Etc/UTC' Local time is now: Sat May 10 15:18:23 UTC 2025. Universal Time is now: Sat May 10 15:18:23 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.21-14) ... Setting up autoconf (2.71-3) ... Setting up sensible-utils (0.0.22) ... Setting up libuchardet0:i386 (0.0.8-1+b1) ... Setting up libsub-override-perl (0.10-1) ... Setting up netbase (6.4) ... Setting up libelf1:i386 (0.190-1+b1) ... Setting up readline-common (8.2-3) ... Setting up libxml2:i386 (2.9.14+dfsg-1.3+b2) ... Setting up automake (1:1.16.5-1.3) ... update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode Setting up libfile-stripnondeterminism-perl (1.13.1-1) ... Setting up gettext (0.21-14+b1) ... Setting up libtool (2.4.7-7) ... Setting up libreadline8:i386 (8.2-3+b1) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up dwz (0.15-1) ... Setting up groff-base (1.23.0-3) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up libpython3.11-stdlib:i386 (3.11.8-1) ... Setting up man-db (2.12.0-3) ... Not building database; man-db/auto-update is not 'true'. Setting up libpython3-stdlib:i386 (3.11.6-1) ... Setting up python3.11 (3.11.8-1) ... Setting up debhelper (13.15.3) ... Setting up python3 (3.11.6-1) ... Setting up python3-lib2to3 (3.11.5-1) ... Setting up python3-pkg-resources (68.1.2-2) ... Setting up python3-distutils (3.11.5-1) ... Setting up python3-setuptools (68.1.2-2) ... Setting up dh-python (6.20240401) ... Processing triggers for libc-bin (2.37-15) ... 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 i386 debian/rules clean dh clean --buildsystem=pybuild --with python3 dh_auto_clean -O--buildsystem=pybuild I: pybuild base:311: python3.11 setup.py clean running clean removing '/build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build' (and everything under it) 'build/bdist.linux-i686' does not exist -- can't clean it 'build/scripts-3.11' 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.11 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.11/build/dmm copying dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm copying dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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.11/build/dmm/modules creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptpkg copying dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptpkg creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptsetup copying dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/cfdisk copying dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/checksums copying dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/checksums copying dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dd copying dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dd copying dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/debootstrap copying dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/download copying dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dpkgsetup copying dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/fallocate copying dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/grub copying dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/linux copying dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/linux copying dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/livedisk copying dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/livedisk copying dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/losetup copying dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/losetup copying dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/losetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/lsblk copying dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/lsblk copying dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mkfs copying dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mkfs copying dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mmdebstrap copying dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mountfs copying dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mountfs copying dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/networking copying dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/networking copying dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/parted copying dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/parted copying dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/readme copying dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/readme copying dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/remove copying dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/reprepro copying dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/squashfs copying dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/umountfs copying dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/umountfs copying dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/users copying dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/users copying dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/vmsetup copying dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/writefile copying dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/xorriso copying dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/xorriso copying dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/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.11/build; python3.11 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s OK 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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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 creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11 creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/dmm.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/__pycache__ copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/__pycache__ copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/livedisk/livedisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/livedisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/livedisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/livedisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptsetup/aptsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/umountfs/umountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/umountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/umountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/umountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptpkg/aptpkg.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptpkg copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/aptpkg/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptpkg creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/checksums/checksums.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/checksums copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/checksums/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/checksums creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/users/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/users copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/users/users.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/users creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/grub copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/grub/grub.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/grub creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/squashfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/squashfs/squashfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/squashfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/lsblk/lsblk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/lsblk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/lsblk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/lsblk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/readme/readme.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/readme copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/readme/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/readme creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/debootstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/debootstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/debootstrap/debootstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/debootstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dpkgsetup/dpkgsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dpkgsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dpkgsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dpkgsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mmdebstrap/mmdebstrap.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mmdebstrap copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mmdebstrap/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mmdebstrap creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/linux/linux.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/linux copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/linux/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/linux creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/download copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/download/download.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/download creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/parted/parted.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/parted copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/parted/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/parted creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/cfdisk/cfdisk.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/cfdisk copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/cfdisk/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/cfdisk creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/vmsetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/vmsetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/vmsetup/vmsetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/vmsetup creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mountfs/mountfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mountfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mountfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mountfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/fallocate copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/fallocate/fallocate.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/fallocate creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/remove copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/remove/remove.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/remove creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/writefile copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/writefile/writefile.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/writefile creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/xorriso/xorriso.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/xorriso copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/xorriso/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/xorriso creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dd/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dd copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/dd/dd.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dd creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mkfs/mkfs.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mkfs copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/mkfs/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mkfs creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/networking/networking.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/networking copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/networking/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/networking creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/reprepro copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/reprepro/reprepro.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/reprepro creating /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/losetup/losetup.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/losetup copying /build/reproducible-path/python3-dmm-0.1.1/.pybuild/cpython3_3.11/build/dmm/modules/losetup/__init__.py -> /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/losetup byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/dmm.py to dmm.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/livedisk/livedisk.py to livedisk.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/livedisk/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptsetup/aptsetup.py to aptsetup.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptsetup/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/umountfs/umountfs.py to umountfs.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/umountfs/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptpkg/aptpkg.py to aptpkg.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/aptpkg/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/checksums/checksums.py to checksums.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/checksums/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/users/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/users/users.py to users.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/grub/grub.py to grub.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/squashfs/squashfs.py to squashfs.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/lsblk/lsblk.py to lsblk.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/lsblk/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/readme/readme.py to readme.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/readme/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/debootstrap/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/debootstrap/debootstrap.py to debootstrap.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dpkgsetup/dpkgsetup.py to dpkgsetup.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dpkgsetup/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mmdebstrap/mmdebstrap.py to mmdebstrap.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mmdebstrap/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/linux/linux.py to linux.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/linux/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/download/download.py to download.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/parted/parted.py to parted.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/parted/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/cfdisk/cfdisk.py to cfdisk.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/cfdisk/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/vmsetup/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/vmsetup/vmsetup.py to vmsetup.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mountfs/mountfs.py to mountfs.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mountfs/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/fallocate/fallocate.py to fallocate.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/remove/remove.py to remove.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/writefile/writefile.py to writefile.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/xorriso/xorriso.py to xorriso.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/xorriso/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dd/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/dd/dd.py to dd.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mkfs/mkfs.py to mkfs.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/mkfs/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/networking/networking.py to networking.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/networking/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/reprepro/reprepro.py to reprepro.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/losetup/losetup.py to losetup.cpython-311.pyc byte-compiling /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/dist-packages/dmm/modules/losetup/__init__.py to __init__.cpython-311.pyc running install_egg_info Copying dmm_highvoltage.egg-info to /build/reproducible-path/python3-dmm-0.1.1/debian/tmp/usr/lib/python3.11/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_i386.buildinfo dpkg-genchanges --build=binary -O../python3-dmm_0.1.1-1_i386.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/109132 and its subdirectories I: Current time: Sat May 10 03:18:35 -12 2025 I: pbuilder-time-stamp: 1746890315 Sun Apr 7 08:55:38 UTC 2024 I: 1st build successful. Starting 2nd build on remote node ionos12-i386.debian.net. Sun Apr 7 08:55:38 UTC 2024 I: Preparing to do remote build '2' on ionos12-i386.debian.net. Sun Apr 7 08:56:37 UTC 2024 I: Deleting $TMPDIR on ionos12-i386.debian.net. Sun Apr 7 08:56:38 UTC 2024 I: python3-dmm_0.1.1-1_i386.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 bac991d50afb0f28ae67c5fcc825c0b0ecd6dd40 5984 python3-dmm_0.1.1-1_i386.buildinfo Checksums-Sha256: e3b142f63fd38f3a42102be43977f0922faa7b7ac6cfbf127d1b23bd4d974201 216984 dmm-utils_0.1.1-1_all.deb f4d68811bd44477bba7891a1c300ab6d618b296636ec30bd733f95947cc3f067 12224 python3-dmm_0.1.1-1_all.deb 5538e3651d24359841d976cdb812c049ac7a44ac3b142f60ddea1c17be8223e7 5984 python3-dmm_0.1.1-1_i386.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 2bbe33a34fa1f7d82768c63d01add2ed 5984 python optional python3-dmm_0.1.1-1_i386.buildinfo Sun Apr 7 08:56:39 UTC 2024 I: diffoscope 263 will be used to compare the two builds: Running as unit: rb-diffoscope-i386_6-19227.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.AKOvzu8n/python3-dmm_0.1.1-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.AKOvzu8n/python3-dmm_0.1.1-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.AKOvzu8n/python3-dmm_0.1.1-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.AKOvzu8n/b1/python3-dmm_0.1.1-1_i386.changes /srv/reproducible-results/rbuild-debian/r-b-build.AKOvzu8n/b2/python3-dmm_0.1.1-1_i386.changes ## command (total time: 0.000s) 0.000s 1 call cmp (internal) ## has_same_content_as (total time: 0.000s) 0.000s 1 call abc.DotChangesFile ## main (total time: 0.323s) 0.323s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.018s) 0.018s 12 calls diffoscope.comparators.binary.FilesystemFile ## specialize (total time: 0.000s) 0.000s 1 call specialize Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 634ms CPU time consumed: 634ms Sun Apr 7 08:56:40 UTC 2024 I: diffoscope 263 found no differences in the changes files, and a .buildinfo file also exists. Sun Apr 7 08:56:40 UTC 2024 I: python3-dmm from trixie built successfully and reproducibly on i386. Sun Apr 7 08:56:41 UTC 2024 I: Submitting .buildinfo files to external archives: Sun Apr 7 08:56:41 UTC 2024 I: Submitting 8.0K b1/python3-dmm_0.1.1-1_i386.buildinfo.asc Sun Apr 7 08:56:42 UTC 2024 I: Submitting 8.0K b2/python3-dmm_0.1.1-1_i386.buildinfo.asc Sun Apr 7 08:56:43 UTC 2024 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Sun Apr 7 08:56:43 UTC 2024 I: Done submitting .buildinfo files. Sun Apr 7 08:56:43 UTC 2024 I: Removing signed python3-dmm_0.1.1-1_i386.buildinfo.asc files: removed './b1/python3-dmm_0.1.1-1_i386.buildinfo.asc' removed './b2/python3-dmm_0.1.1-1_i386.buildinfo.asc'