Running as unit: rb-build-arm64_16-38213.service ==================================================================================== Mon Nov 25 12:52:03 UTC 2024 - running /srv/jenkins/bin/reproducible_build.sh (for job reproducible_builder_arm64_16) on jenkins, called using "codethink02-arm64 codethink01-arm64" as arguments. Mon Nov 25 12:52:03 UTC 2024 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-60GYEpoh" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Mon Nov 25 12:52:04 UTC 2024 - checking /var/lib/jenkins/offline_nodes if codethink02-arm64.debian.net is marked as down. Mon Nov 25 12:52:04 UTC 2024 - checking via ssh if codethink02-arm64.debian.net is up. removed '/tmp/read-only-fs-test-xh1zAI' Mon Nov 25 12:52:04 UTC 2024 - checking /var/lib/jenkins/offline_nodes if codethink01-arm64.debian.net is marked as down. Mon Nov 25 12:52:04 UTC 2024 - checking via ssh if codethink01-arm64.debian.net is up. removed '/tmp/read-only-fs-test-Wfy6ES' ok, let's check if python-django-registration is building anywhere yet… ok, python-django-registration is not building anywhere… UPDATE 1 ============================================================================= Initialising reproducibly build of python-django-registration in unstable on arm64 on jenkins now. 1st build will be done on codethink02-arm64.debian.net. 2nd build will be done on codethink01-arm64.debian.net. ============================================================================= Mon Nov 25 12:52:12 UTC 2024 I: starting to build python-django-registration/unstable/arm64 on jenkins on '2024-11-25 12:52' Mon Nov 25 12:52:13 UTC 2024 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/arm64_16/38213/console.log 1732539133 arm64 unstable python-django-registration Mon Nov 25 12:52:13 UTC 2024 I: Downloading source for unstable/python-django-registration=3.3-1 --2024-11-25 12:52:13-- http://deb.debian.org/debian/pool/main/p/python-django-registration/python-django-registration_3.3-1.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2355 (2.3K) [text/prs.lines.tag] Saving to: ‘python-django-registration_3.3-1.dsc’ 0K .. 100% 88.7M=0s 2024-11-25 12:52:13 (88.7 MB/s) - ‘python-django-registration_3.3-1.dsc’ saved [2355/2355] --2024-11-25 12:52:13-- http://deb.debian.org/debian/pool/main/p/python-django-registration/python-django-registration_3.3-1.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2355 (2.3K) [text/prs.lines.tag] Saving to: ‘python-django-registration_3.3-1.dsc’ 0K .. 100% 88.7M=0s 2024-11-25 12:52:13 (88.7 MB/s) - ‘python-django-registration_3.3-1.dsc’ saved [2355/2355] Mon Nov 25 12:52:13 UTC 2024 I: python-django-registration_3.3-1.dsc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 3.0 (quilt) Source: python-django-registration Binary: python3-django-registration, python-django-registration-doc Architecture: all Version: 3.3-1 Maintainer: Debian Python Team Uploaders: Stephan Peijnik , Stephan Sürken Homepage: https://github.com/ubernostrum/django-registration Standards-Version: 4.6.1.0 Vcs-Browser: https://salsa.debian.org/python-team/packages/python-django-registration Vcs-Git: https://salsa.debian.org/python-team/packages/python-django-registration.git Build-Depends: debhelper-compat (= 13), dh-python, python3-all Build-Depends-Indep: python3-setuptools, python3-confusable-homoglyphs (>= 3), python3-django, python3-sphinx, python3-sphinx-rtd-theme Package-List: python-django-registration-doc deb doc optional arch=all python3-django-registration deb python optional arch=all Checksums-Sha1: f32b1acf3492f5196731a0b55272d9fde370e872 85046 python-django-registration_3.3.orig.tar.gz 754fcd16a3a00eba22f2b1f8480b968eb00dae91 833 python-django-registration_3.3.orig.tar.gz.asc 8299d00ffc0558e4e0e8913ad456c167c235536a 10396 python-django-registration_3.3-1.debian.tar.xz Checksums-Sha256: 884a4cc9ec87b9f1c0ceb6b6c4b7ba491c1877997a3cd29cc923697dac785eb8 85046 python-django-registration_3.3.orig.tar.gz 182a64c844b53a052963bddc85c0f1a137fce8ffbf29183b20279524f4791d87 833 python-django-registration_3.3.orig.tar.gz.asc 8fef0e3cbd620026bbb4a52e12b57c43cd64f15f9b4e241c7633ab0400402ca3 10396 python-django-registration_3.3-1.debian.tar.xz Files: 7126617224057707f3b262757a3dcf06 85046 python-django-registration_3.3.orig.tar.gz 43165b98c940733803dc9f8921446463 833 python-django-registration_3.3.orig.tar.gz.asc 4f52a8ee19c8e0d05e794569748d944d 10396 python-django-registration_3.3-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEY8n6rGg5PpTPkl4ZcL0i0xEjtDEFAmNWeOEACgkQcL0i0xEj tDGEoAf8DzFLxDeQFsWWl4RRasEYkV8W/9V3H+tFWL8kl0dr2qHm12JXzbnLftxn /DKJGkO9CTti4mIS4XI0SEnIjlGyTtpB6qC7y8zFTgvePkIHIqz6tAUGslw/Rsb2 DVK8IrIc9Mi2smpsQ2H4ve4dEyEuiNxunAn/DL2rcClinRVMFrWouEnRUPJnKfMK TpTh7mEo0W0AEcmSUw9oQO6INX0Iqvdl2pMsUPqcHqZF7oAwa4P9FvoKy/ZAvera +sF5YcBlryBjeDsPX6TRdPqnCpzTTf8o1Kyq7s8vNZ/2N6aOQtfSgdIrues9+qNL Ad+m/EcTjlZ2hLILI6rbr67GITQqBQ== =uRkj -----END PGP SIGNATURE----- Mon Nov 25 12:52:13 UTC 2024 I: Checking whether the package is not for us Mon Nov 25 12:52:13 UTC 2024 I: Starting 1st build on remote node codethink02-arm64.debian.net. Mon Nov 25 12:52:13 UTC 2024 I: Preparing to do remote build '1' on codethink02-arm64.debian.net. Mon Nov 25 12:52:13 UTC 2024 - checking /var/lib/jenkins/offline_nodes if codethink02-arm64.debian.net is marked as down. Mon Nov 25 12:52:13 UTC 2024 - checking via ssh if codethink02-arm64.debian.net is up. removed '/tmp/read-only-fs-test-kW5d9V' ==================================================================================== Mon Nov 25 12:52:14 UTC 2024 - running /srv/jenkins/bin/reproducible_build.sh (for job /srv/jenkins/bin/reproducible_build.sh) on codethink02-arm64, called using "1 python-django-registration unstable /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy 3.3-1" as arguments. Mon Nov 25 12:52:14 UTC 2024 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-VXvkTbYo" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Mon Nov 25 12:52:14 UTC 2024 I: Downloading source for unstable/python-django-registration=3.3-1 Reading package lists... NOTICE: 'python-django-registration' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/python-team/packages/python-django-registration.git Please use: git clone https://salsa.debian.org/python-team/packages/python-django-registration.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 98.6 kB of source archives. Get:1 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (dsc) [2355 B] Get:2 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (tar) [85.0 kB] Get:3 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (asc) [833 B] Get:4 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (diff) [10.4 kB] Fetched 98.6 kB in 0s (1805 kB/s) Download complete and in download only mode Reading package lists... NOTICE: 'python-django-registration' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/python-team/packages/python-django-registration.git Please use: git clone https://salsa.debian.org/python-team/packages/python-django-registration.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 98.6 kB of source archives. Get:1 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (dsc) [2355 B] Get:2 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (tar) [85.0 kB] Get:3 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (asc) [833 B] Get:4 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (diff) [10.4 kB] Fetched 98.6 kB in 0s (1805 kB/s) Download complete and in download only mode ============================================================================= Building python-django-registration in unstable on arm64 on codethink02-arm64 now. Date: Mon Nov 25 12:52:15 GMT 2024 Date UTC: Mon Nov 25 12:52:15 UTC 2024 ============================================================================= W: /root/.pbuilderrc does not exist I: Logging to b1/build.log I: pbuilder: network access will be disabled during build I: Current time: Mon Nov 25 00:52:15 -12 2024 I: pbuilder-time-stamp: 1732539135 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Copying source file I: copying [python-django-registration_3.3-1.dsc] I: copying [./python-django-registration_3.3.orig.tar.gz] I: copying [./python-django-registration_3.3.orig.tar.gz.asc] I: copying [./python-django-registration_3.3-1.debian.tar.xz] I: Extracting source gpgv: Signature made Mon Oct 24 11:37:05 2022 gpgv: using RSA key 63C9FAAC68393E94CF925E1970BD22D31123B431 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./python-django-registration_3.3-1.dsc: no acceptable signature found dpkg-source: info: extracting python-django-registration in python-django-registration-3.3 dpkg-source: info: unpacking python-django-registration_3.3.orig.tar.gz dpkg-source: info: unpacking python-django-registration_3.3-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/3825326/tmp/hooks/D02_print_environment starting I: set BUILDDIR='/build/reproducible-path' BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' BUILDUSERNAME='pbuilder1' BUILD_ARCH='arm64' DEBIAN_FRONTEND='noninteractive' DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' DISTRIBUTION='unstable' HOME='/root' HOST_ARCH='arm64' IFS=' ' INVOCATION_ID='0e0b7970444f480989ce537bf542d0e0' LANG='C' LANGUAGE='en_US:en' LC_ALL='C' MAIL='/var/mail/root' OPTIND='1' PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' PBCURRENTCOMMANDLINEOPERATION='build' PBUILDER_OPERATION='build' PBUILDER_PKGDATADIR='/usr/share/pbuilder' PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' PBUILDER_SYSCONFDIR='/etc' PPID='3825326' 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.SUQ9kGBy/pbuilderrc_acZp --distribution unstable --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1 --logfile b1/build.log python-django-registration_3.3-1.dsc' SUDO_GID='109' SUDO_UID='104' SUDO_USER='jenkins' TERM='unknown' TZ='/usr/share/zoneinfo/Etc/GMT+12' USER='root' _='/usr/bin/systemd-run' http_proxy='http://192.168.101.4:3128' I: uname -a Linux codethink02-arm64 6.1.0-28-cloud-arm64 #1 SMP Debian 6.1.119-1 (2024-11-22) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Nov 22 14:40 /bin -> usr/bin I: user script /srv/workspace/pbuilder/3825326/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: arm64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper-compat (= 13), dh-python, python3-all, python3-setuptools, python3-confusable-homoglyphs (>= 3), python3-django, python3-sphinx, python3-sphinx-rtd-theme dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20083 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-all; however: Package python3-all is not installed. pbuilder-satisfydepends-dummy depends on python3-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3-confusable-homoglyphs (>= 3); however: Package python3-confusable-homoglyphs is not installed. pbuilder-satisfydepends-dummy depends on python3-django; however: Package python3-django is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx; however: Package python3-sphinx is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx-rtd-theme; however: Package python3-sphinx-rtd-theme 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} ca-certificates{a} debhelper{a} dh-autoreconf{a} dh-python{a} dh-strip-nondeterminism{a} docutils-common{a} dwz{a} file{a} fonts-font-awesome{a} fonts-lato{a} gettext{a} gettext-base{a} groff-base{a} intltool-debian{a} libarchive-zip-perl{a} libcom-err2{a} libdebhelper-perl{a} libelf1t64{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libgssapi-krb5-2{a} libicu72{a} libjs-jquery{a} libjs-sphinxdoc{a} libjs-underscore{a} libjson-perl{a} libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} libmagic-mgc{a} libmagic1t64{a} libnsl2{a} libpipeline1{a} libpython3-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libpython3.13-minimal{a} libpython3.13-stdlib{a} libreadline8t64{a} libtirpc-common{a} libtirpc3t64{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} po-debconf{a} python-babel-localedata{a} python3{a} python3-alabaster{a} python3-all{a} python3-asgiref{a} python3-autocommand{a} python3-babel{a} python3-certifi{a} python3-chardet{a} python3-charset-normalizer{a} python3-confusable-homoglyphs{a} python3-defusedxml{a} python3-django{a} python3-docutils{a} python3-idna{a} python3-imagesize{a} python3-inflect{a} python3-jaraco.context{a} python3-jaraco.functools{a} python3-jaraco.text{a} python3-jinja2{a} python3-markupsafe{a} python3-minimal{a} python3-more-itertools{a} python3-packaging{a} python3-pkg-resources{a} python3-pygments{a} python3-requests{a} python3-roman{a} python3-setuptools{a} python3-snowballstemmer{a} python3-sphinx{a} python3-sphinx-rtd-theme{a} python3-sphinxcontrib.jquery{a} python3-sqlparse{a} python3-typeguard{a} python3-typing-extensions{a} python3-urllib3{a} python3-zipp{a} python3.12{a} python3.12-minimal{a} python3.13{a} python3.13-minimal{a} readline-common{a} sensible-utils{a} sgml-base{a} sphinx-common{a} sphinx-rtd-theme-common{a} tzdata{a} xml-core{a} The following packages are RECOMMENDED but will NOT be installed: curl javascript-common krb5-locales libarchive-cpio-perl libjson-xs-perl libltdl-dev libmail-sendmail-perl libpaper-utils lynx python3-click python3-pil python3-tz wget 0 packages upgraded, 106 newly installed, 0 to remove and 0 not upgraded. Need to get 51.6 MB of archives. After unpacking 234 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian unstable/main arm64 fonts-lato all 2.015-1 [2780 kB] Get: 2 http://deb.debian.org/debian unstable/main arm64 libpython3.12-minimal arm64 3.12.7-3 [808 kB] Get: 3 http://deb.debian.org/debian unstable/main arm64 libexpat1 arm64 2.6.4-1 [90.7 kB] Get: 4 http://deb.debian.org/debian unstable/main arm64 python3.12-minimal arm64 3.12.7-3 [1940 kB] Get: 5 http://deb.debian.org/debian unstable/main arm64 python3-minimal arm64 3.12.7-1 [26.8 kB] Get: 6 http://deb.debian.org/debian unstable/main arm64 media-types all 10.1.0 [26.9 kB] Get: 7 http://deb.debian.org/debian unstable/main arm64 netbase all 6.4 [12.8 kB] Get: 8 http://deb.debian.org/debian unstable/main arm64 tzdata all 2024b-3 [255 kB] Get: 9 http://deb.debian.org/debian unstable/main arm64 libkrb5support0 arm64 1.21.3-3 [32.1 kB] Get: 10 http://deb.debian.org/debian unstable/main arm64 libcom-err2 arm64 1.47.1-1+b1 [23.1 kB] Get: 11 http://deb.debian.org/debian unstable/main arm64 libk5crypto3 arm64 1.21.3-3 [80.8 kB] Get: 12 http://deb.debian.org/debian unstable/main arm64 libkeyutils1 arm64 1.6.3-4 [9352 B] Get: 13 http://deb.debian.org/debian unstable/main arm64 libkrb5-3 arm64 1.21.3-3 [310 kB] Get: 14 http://deb.debian.org/debian unstable/main arm64 libgssapi-krb5-2 arm64 1.21.3-3 [126 kB] Get: 15 http://deb.debian.org/debian unstable/main arm64 libtirpc-common all 1.3.4+ds-1.3 [10.9 kB] Get: 16 http://deb.debian.org/debian unstable/main arm64 libtirpc3t64 arm64 1.3.4+ds-1.3+b1 [78.7 kB] Get: 17 http://deb.debian.org/debian unstable/main arm64 libnsl2 arm64 1.3.0-3+b3 [37.9 kB] Get: 18 http://deb.debian.org/debian unstable/main arm64 readline-common all 8.2-5 [69.3 kB] Get: 19 http://deb.debian.org/debian unstable/main arm64 libreadline8t64 arm64 8.2-5 [159 kB] Get: 20 http://deb.debian.org/debian unstable/main arm64 libpython3.12-stdlib arm64 3.12.7-3 [1902 kB] Get: 21 http://deb.debian.org/debian unstable/main arm64 python3.12 arm64 3.12.7-3 [671 kB] Get: 22 http://deb.debian.org/debian unstable/main arm64 libpython3-stdlib arm64 3.12.7-1 [9708 B] Get: 23 http://deb.debian.org/debian unstable/main arm64 python3 arm64 3.12.7-1 [27.8 kB] Get: 24 http://deb.debian.org/debian unstable/main arm64 libpython3.13-minimal arm64 3.13.0-2 [850 kB] Get: 25 http://deb.debian.org/debian unstable/main arm64 python3.13-minimal arm64 3.13.0-2 [1838 kB] Get: 26 http://deb.debian.org/debian unstable/main arm64 sgml-base all 1.31 [15.4 kB] Get: 27 http://deb.debian.org/debian unstable/main arm64 sensible-utils all 0.0.24 [24.8 kB] Get: 28 http://deb.debian.org/debian unstable/main arm64 openssl arm64 3.3.2-2 [1347 kB] Get: 29 http://deb.debian.org/debian unstable/main arm64 ca-certificates all 20240203 [158 kB] Get: 30 http://deb.debian.org/debian unstable/main arm64 libmagic-mgc arm64 1:5.45-3+b1 [314 kB] Get: 31 http://deb.debian.org/debian unstable/main arm64 libmagic1t64 arm64 1:5.45-3+b1 [102 kB] Get: 32 http://deb.debian.org/debian unstable/main arm64 file arm64 1:5.45-3+b1 [43.4 kB] Get: 33 http://deb.debian.org/debian unstable/main arm64 gettext-base arm64 0.22.5-2 [198 kB] Get: 34 http://deb.debian.org/debian unstable/main arm64 libuchardet0 arm64 0.0.8-1+b2 [69.2 kB] Get: 35 http://deb.debian.org/debian unstable/main arm64 groff-base arm64 1.23.0-5 [1129 kB] Get: 36 http://deb.debian.org/debian unstable/main arm64 bsdextrautils arm64 2.40.2-11 [91.2 kB] Get: 37 http://deb.debian.org/debian unstable/main arm64 libpipeline1 arm64 1.5.8-1 [40.2 kB] Get: 38 http://deb.debian.org/debian unstable/main arm64 man-db arm64 2.13.0-1 [1404 kB] Get: 39 http://deb.debian.org/debian unstable/main arm64 m4 arm64 1.4.19-4 [277 kB] Get: 40 http://deb.debian.org/debian unstable/main arm64 autoconf all 2.72-3 [493 kB] Get: 41 http://deb.debian.org/debian unstable/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 42 http://deb.debian.org/debian unstable/main arm64 automake all 1:1.16.5-1.3 [823 kB] Get: 43 http://deb.debian.org/debian unstable/main arm64 autopoint all 0.22.5-2 [723 kB] Get: 44 http://deb.debian.org/debian unstable/main arm64 libdebhelper-perl all 13.20 [89.7 kB] Get: 45 http://deb.debian.org/debian unstable/main arm64 libtool all 2.4.7-8 [517 kB] Get: 46 http://deb.debian.org/debian unstable/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 47 http://deb.debian.org/debian unstable/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 48 http://deb.debian.org/debian unstable/main arm64 libfile-stripnondeterminism-perl all 1.14.0-1 [19.5 kB] Get: 49 http://deb.debian.org/debian unstable/main arm64 dh-strip-nondeterminism all 1.14.0-1 [8448 B] Get: 50 http://deb.debian.org/debian unstable/main arm64 libelf1t64 arm64 0.192-4 [189 kB] Get: 51 http://deb.debian.org/debian unstable/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 52 http://deb.debian.org/debian unstable/main arm64 libicu72 arm64 72.1-5+b1 [9239 kB] Get: 53 http://deb.debian.org/debian unstable/main arm64 libxml2 arm64 2.12.7+dfsg+really2.9.14-0.2+b1 [630 kB] Get: 54 http://deb.debian.org/debian unstable/main arm64 gettext arm64 0.22.5-2 [1532 kB] Get: 55 http://deb.debian.org/debian unstable/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 56 http://deb.debian.org/debian unstable/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 57 http://deb.debian.org/debian unstable/main arm64 debhelper all 13.20 [915 kB] Get: 58 http://deb.debian.org/debian unstable/main arm64 python3-autocommand all 2.2.2-3 [13.6 kB] Get: 59 http://deb.debian.org/debian unstable/main arm64 python3-more-itertools all 10.5.0-1 [63.8 kB] Get: 60 http://deb.debian.org/debian unstable/main arm64 python3-typing-extensions all 4.12.2-2 [73.0 kB] Get: 61 http://deb.debian.org/debian unstable/main arm64 python3-typeguard all 4.4.1-1 [37.0 kB] Get: 62 http://deb.debian.org/debian unstable/main arm64 python3-inflect all 7.3.1-2 [32.4 kB] Get: 63 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.context all 6.0.0-1 [7984 B] Get: 64 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.functools all 4.1.0-1 [12.0 kB] Get: 65 http://deb.debian.org/debian unstable/main arm64 python3-pkg-resources all 75.2.0-1 [213 kB] Get: 66 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.text all 4.0.0-1 [11.4 kB] Get: 67 http://deb.debian.org/debian unstable/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 68 http://deb.debian.org/debian unstable/main arm64 python3-setuptools all 75.2.0-1 [731 kB] Get: 69 http://deb.debian.org/debian unstable/main arm64 dh-python all 6.20241024 [109 kB] Get: 70 http://deb.debian.org/debian unstable/main arm64 xml-core all 0.19 [20.1 kB] Get: 71 http://deb.debian.org/debian unstable/main arm64 docutils-common all 0.21.2+dfsg-2 [128 kB] Get: 72 http://deb.debian.org/debian unstable/main arm64 fonts-font-awesome all 5.0.10+really4.7.0~dfsg-4.1 [517 kB] Get: 73 http://deb.debian.org/debian unstable/main arm64 libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get: 74 http://deb.debian.org/debian unstable/main arm64 libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get: 75 http://deb.debian.org/debian unstable/main arm64 libjs-sphinxdoc all 7.4.7-4 [158 kB] Get: 76 http://deb.debian.org/debian unstable/main arm64 libjson-perl all 4.10000-1 [87.5 kB] Get: 77 http://deb.debian.org/debian unstable/main arm64 libpython3.13-stdlib arm64 3.13.0-2 [1922 kB] Get: 78 http://deb.debian.org/debian unstable/main arm64 python-babel-localedata all 2.16.0-1 [5696 kB] Get: 79 http://deb.debian.org/debian unstable/main arm64 python3-alabaster all 0.7.16-0.1 [27.9 kB] Get: 80 http://deb.debian.org/debian unstable/main arm64 python3.13 arm64 3.13.0-2 [730 kB] Get: 81 http://deb.debian.org/debian unstable/main arm64 python3-all arm64 3.12.7-1 [1052 B] Get: 82 http://deb.debian.org/debian unstable/main arm64 python3-asgiref all 3.8.1-1 [28.8 kB] Get: 83 http://deb.debian.org/debian unstable/main arm64 python3-babel all 2.16.0-1 [114 kB] Get: 84 http://deb.debian.org/debian unstable/main arm64 python3-certifi all 2024.8.30+dfsg-1 [9576 B] Get: 85 http://deb.debian.org/debian unstable/main arm64 python3-chardet all 5.2.0+dfsg-1 [107 kB] Get: 86 http://deb.debian.org/debian unstable/main arm64 python3-charset-normalizer arm64 3.4.0-1+b1 [129 kB] Get: 87 http://deb.debian.org/debian unstable/main arm64 python3-confusable-homoglyphs all 3.3.1-1 [128 kB] Get: 88 http://deb.debian.org/debian unstable/main arm64 python3-defusedxml all 0.7.1-2 [43.3 kB] Get: 89 http://deb.debian.org/debian unstable/main arm64 python3-sqlparse all 0.5.2-1 [39.7 kB] Get: 90 http://deb.debian.org/debian unstable/main arm64 python3-django all 3:4.2.16-1 [2738 kB] Get: 91 http://deb.debian.org/debian unstable/main arm64 python3-roman all 4.2-1 [10.4 kB] Get: 92 http://deb.debian.org/debian unstable/main arm64 python3-docutils all 0.21.2+dfsg-2 [403 kB] Get: 93 http://deb.debian.org/debian unstable/main arm64 python3-idna all 3.8-2 [41.6 kB] Get: 94 http://deb.debian.org/debian unstable/main arm64 python3-imagesize all 1.4.1-1 [6688 B] Get: 95 http://deb.debian.org/debian unstable/main arm64 python3-markupsafe arm64 2.1.5-1+b3 [14.0 kB] Get: 96 http://deb.debian.org/debian unstable/main arm64 python3-jinja2 all 3.1.3-1 [119 kB] Get: 97 http://deb.debian.org/debian unstable/main arm64 python3-packaging all 24.2-1 [55.3 kB] Get: 98 http://deb.debian.org/debian unstable/main arm64 python3-pygments all 2.18.0+dfsg-1 [836 kB] Get: 99 http://deb.debian.org/debian unstable/main arm64 python3-urllib3 all 2.0.7-2 [111 kB] Get: 100 http://deb.debian.org/debian unstable/main arm64 python3-requests all 2.32.3+dfsg-1 [71.9 kB] Get: 101 http://deb.debian.org/debian unstable/main arm64 python3-snowballstemmer all 2.2.0-4 [58.0 kB] Get: 102 http://deb.debian.org/debian unstable/main arm64 sphinx-common all 7.4.7-4 [731 kB] Get: 103 http://deb.debian.org/debian unstable/main arm64 python3-sphinx all 7.4.7-4 [588 kB] Get: 104 http://deb.debian.org/debian unstable/main arm64 sphinx-rtd-theme-common all 3.0.2+dfsg-1 [1023 kB] Get: 105 http://deb.debian.org/debian unstable/main arm64 python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 106 http://deb.debian.org/debian unstable/main arm64 python3-sphinx-rtd-theme all 3.0.2+dfsg-1 [29.5 kB] Fetched 51.6 MB in 0s (189 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package fonts-lato. (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 ... 20083 files and directories currently installed.) Preparing to unpack .../fonts-lato_2.015-1_all.deb ... Unpacking fonts-lato (2.015-1) ... Selecting previously unselected package libpython3.12-minimal:arm64. Preparing to unpack .../libpython3.12-minimal_3.12.7-3_arm64.deb ... Unpacking libpython3.12-minimal:arm64 (3.12.7-3) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.4-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.4-1) ... Selecting previously unselected package python3.12-minimal. Preparing to unpack .../python3.12-minimal_3.12.7-3_arm64.deb ... Unpacking python3.12-minimal (3.12.7-3) ... Setting up libpython3.12-minimal:arm64 (3.12.7-3) ... Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.12-minimal (3.12.7-3) ... 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 ... 20429 files and directories currently installed.) Preparing to unpack .../00-python3-minimal_3.12.7-1_arm64.deb ... Unpacking python3-minimal (3.12.7-1) ... Selecting previously unselected package media-types. Preparing to unpack .../01-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../02-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package tzdata. Preparing to unpack .../03-tzdata_2024b-3_all.deb ... Unpacking tzdata (2024b-3) ... Selecting previously unselected package libkrb5support0:arm64. Preparing to unpack .../04-libkrb5support0_1.21.3-3_arm64.deb ... Unpacking libkrb5support0:arm64 (1.21.3-3) ... Selecting previously unselected package libcom-err2:arm64. Preparing to unpack .../05-libcom-err2_1.47.1-1+b1_arm64.deb ... Unpacking libcom-err2:arm64 (1.47.1-1+b1) ... Selecting previously unselected package libk5crypto3:arm64. Preparing to unpack .../06-libk5crypto3_1.21.3-3_arm64.deb ... Unpacking libk5crypto3:arm64 (1.21.3-3) ... Selecting previously unselected package libkeyutils1:arm64. Preparing to unpack .../07-libkeyutils1_1.6.3-4_arm64.deb ... Unpacking libkeyutils1:arm64 (1.6.3-4) ... Selecting previously unselected package libkrb5-3:arm64. Preparing to unpack .../08-libkrb5-3_1.21.3-3_arm64.deb ... Unpacking libkrb5-3:arm64 (1.21.3-3) ... Selecting previously unselected package libgssapi-krb5-2:arm64. Preparing to unpack .../09-libgssapi-krb5-2_1.21.3-3_arm64.deb ... Unpacking libgssapi-krb5-2:arm64 (1.21.3-3) ... Selecting previously unselected package libtirpc-common. Preparing to unpack .../10-libtirpc-common_1.3.4+ds-1.3_all.deb ... Unpacking libtirpc-common (1.3.4+ds-1.3) ... Selecting previously unselected package libtirpc3t64:arm64. Preparing to unpack .../11-libtirpc3t64_1.3.4+ds-1.3+b1_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libtirpc.so.3 to /lib/aarch64-linux-gnu/libtirpc.so.3.usr-is-merged by libtirpc3t64' Adding 'diversion of /lib/aarch64-linux-gnu/libtirpc.so.3.0.0 to /lib/aarch64-linux-gnu/libtirpc.so.3.0.0.usr-is-merged by libtirpc3t64' Unpacking libtirpc3t64:arm64 (1.3.4+ds-1.3+b1) ... Selecting previously unselected package libnsl2:arm64. Preparing to unpack .../12-libnsl2_1.3.0-3+b3_arm64.deb ... Unpacking libnsl2:arm64 (1.3.0-3+b3) ... Selecting previously unselected package readline-common. Preparing to unpack .../13-readline-common_8.2-5_all.deb ... Unpacking readline-common (8.2-5) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../14-libreadline8t64_8.2-5_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8 to /lib/aarch64-linux-gnu/libhistory.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8.2 to /lib/aarch64-linux-gnu/libhistory.so.8.2.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8 to /lib/aarch64-linux-gnu/libreadline.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8.2 to /lib/aarch64-linux-gnu/libreadline.so.8.2.usr-is-merged by libreadline8t64' Unpacking libreadline8t64:arm64 (8.2-5) ... Selecting previously unselected package libpython3.12-stdlib:arm64. Preparing to unpack .../15-libpython3.12-stdlib_3.12.7-3_arm64.deb ... Unpacking libpython3.12-stdlib:arm64 (3.12.7-3) ... Selecting previously unselected package python3.12. Preparing to unpack .../16-python3.12_3.12.7-3_arm64.deb ... Unpacking python3.12 (3.12.7-3) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../17-libpython3-stdlib_3.12.7-1_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.12.7-1) ... Setting up python3-minimal (3.12.7-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 ... 21491 files and directories currently installed.) Preparing to unpack .../00-python3_3.12.7-1_arm64.deb ... Unpacking python3 (3.12.7-1) ... Selecting previously unselected package libpython3.13-minimal:arm64. Preparing to unpack .../01-libpython3.13-minimal_3.13.0-2_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.0-2) ... Selecting previously unselected package python3.13-minimal. Preparing to unpack .../02-python3.13-minimal_3.13.0-2_arm64.deb ... Unpacking python3.13-minimal (3.13.0-2) ... Selecting previously unselected package sgml-base. Preparing to unpack .../03-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../04-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package openssl. Preparing to unpack .../05-openssl_3.3.2-2_arm64.deb ... Unpacking openssl (3.3.2-2) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../06-ca-certificates_20240203_all.deb ... Unpacking ca-certificates (20240203) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../07-libmagic-mgc_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3+b1) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../08-libmagic1t64_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3+b1) ... Selecting previously unselected package file. Preparing to unpack .../09-file_1%3a5.45-3+b1_arm64.deb ... Unpacking file (1:5.45-3+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../10-gettext-base_0.22.5-2_arm64.deb ... Unpacking gettext-base (0.22.5-2) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../11-libuchardet0_0.0.8-1+b2_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b2) ... Selecting previously unselected package groff-base. Preparing to unpack .../12-groff-base_1.23.0-5_arm64.deb ... Unpacking groff-base (1.23.0-5) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../13-bsdextrautils_2.40.2-11_arm64.deb ... Unpacking bsdextrautils (2.40.2-11) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../14-libpipeline1_1.5.8-1_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../15-man-db_2.13.0-1_arm64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../16-m4_1.4.19-4_arm64.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../17-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../18-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../19-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 .../20-autopoint_0.22.5-2_all.deb ... Unpacking autopoint (0.22.5-2) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../21-libdebhelper-perl_13.20_all.deb ... Unpacking libdebhelper-perl (13.20) ... Selecting previously unselected package libtool. Preparing to unpack .../22-libtool_2.4.7-8_all.deb ... Unpacking libtool (2.4.7-8) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../23-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../24-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../25-libfile-stripnondeterminism-perl_1.14.0-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.0-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../26-dh-strip-nondeterminism_1.14.0-1_all.deb ... Unpacking dh-strip-nondeterminism (1.14.0-1) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../27-libelf1t64_0.192-4_arm64.deb ... Unpacking libelf1t64:arm64 (0.192-4) ... Selecting previously unselected package dwz. Preparing to unpack .../28-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../29-libicu72_72.1-5+b1_arm64.deb ... Unpacking libicu72:arm64 (72.1-5+b1) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../30-libxml2_2.12.7+dfsg+really2.9.14-0.2+b1_arm64.deb ... Unpacking libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Selecting previously unselected package gettext. Preparing to unpack .../31-gettext_0.22.5-2_arm64.deb ... Unpacking gettext (0.22.5-2) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../32-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 .../33-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../34-debhelper_13.20_all.deb ... Unpacking debhelper (13.20) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../35-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../36-python3-more-itertools_10.5.0-1_all.deb ... Unpacking python3-more-itertools (10.5.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../37-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../38-python3-typeguard_4.4.1-1_all.deb ... Unpacking python3-typeguard (4.4.1-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../39-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../40-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../41-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../42-python3-pkg-resources_75.2.0-1_all.deb ... Unpacking python3-pkg-resources (75.2.0-1) ... Selecting previously unselected package python3-jaraco.text. Preparing to unpack .../43-python3-jaraco.text_4.0.0-1_all.deb ... Unpacking python3-jaraco.text (4.0.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../44-python3-zipp_3.21.0-1_all.deb ... Unpacking python3-zipp (3.21.0-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../45-python3-setuptools_75.2.0-1_all.deb ... Unpacking python3-setuptools (75.2.0-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../46-dh-python_6.20241024_all.deb ... Unpacking dh-python (6.20241024) ... Selecting previously unselected package xml-core. Preparing to unpack .../47-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../48-docutils-common_0.21.2+dfsg-2_all.deb ... Unpacking docutils-common (0.21.2+dfsg-2) ... Selecting previously unselected package fonts-font-awesome. Preparing to unpack .../49-fonts-font-awesome_5.0.10+really4.7.0~dfsg-4.1_all.deb ... Unpacking fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../50-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../51-libjs-underscore_1.13.4~dfsg+~1.11.4-3_all.deb ... Unpacking libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../52-libjs-sphinxdoc_7.4.7-4_all.deb ... Unpacking libjs-sphinxdoc (7.4.7-4) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../53-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package libpython3.13-stdlib:arm64. Preparing to unpack .../54-libpython3.13-stdlib_3.13.0-2_arm64.deb ... Unpacking libpython3.13-stdlib:arm64 (3.13.0-2) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../55-python-babel-localedata_2.16.0-1_all.deb ... Unpacking python-babel-localedata (2.16.0-1) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../56-python3-alabaster_0.7.16-0.1_all.deb ... Unpacking python3-alabaster (0.7.16-0.1) ... Selecting previously unselected package python3.13. Preparing to unpack .../57-python3.13_3.13.0-2_arm64.deb ... Unpacking python3.13 (3.13.0-2) ... Selecting previously unselected package python3-all. Preparing to unpack .../58-python3-all_3.12.7-1_arm64.deb ... Unpacking python3-all (3.12.7-1) ... Selecting previously unselected package python3-asgiref. Preparing to unpack .../59-python3-asgiref_3.8.1-1_all.deb ... Unpacking python3-asgiref (3.8.1-1) ... Selecting previously unselected package python3-babel. Preparing to unpack .../60-python3-babel_2.16.0-1_all.deb ... Unpacking python3-babel (2.16.0-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../61-python3-certifi_2024.8.30+dfsg-1_all.deb ... Unpacking python3-certifi (2024.8.30+dfsg-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../62-python3-chardet_5.2.0+dfsg-1_all.deb ... Unpacking python3-chardet (5.2.0+dfsg-1) ... Selecting previously unselected package python3-charset-normalizer. Preparing to unpack .../63-python3-charset-normalizer_3.4.0-1+b1_arm64.deb ... Unpacking python3-charset-normalizer (3.4.0-1+b1) ... Selecting previously unselected package python3-confusable-homoglyphs. Preparing to unpack .../64-python3-confusable-homoglyphs_3.3.1-1_all.deb ... Unpacking python3-confusable-homoglyphs (3.3.1-1) ... Selecting previously unselected package python3-defusedxml. Preparing to unpack .../65-python3-defusedxml_0.7.1-2_all.deb ... Unpacking python3-defusedxml (0.7.1-2) ... Selecting previously unselected package python3-sqlparse. Preparing to unpack .../66-python3-sqlparse_0.5.2-1_all.deb ... Unpacking python3-sqlparse (0.5.2-1) ... Selecting previously unselected package python3-django. Preparing to unpack .../67-python3-django_3%3a4.2.16-1_all.deb ... Unpacking python3-django (3:4.2.16-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../68-python3-roman_4.2-1_all.deb ... Unpacking python3-roman (4.2-1) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../69-python3-docutils_0.21.2+dfsg-2_all.deb ... Unpacking python3-docutils (0.21.2+dfsg-2) ... Selecting previously unselected package python3-idna. Preparing to unpack .../70-python3-idna_3.8-2_all.deb ... Unpacking python3-idna (3.8-2) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../71-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../72-python3-markupsafe_2.1.5-1+b3_arm64.deb ... Unpacking python3-markupsafe (2.1.5-1+b3) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../73-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../74-python3-packaging_24.2-1_all.deb ... Unpacking python3-packaging (24.2-1) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../75-python3-pygments_2.18.0+dfsg-1_all.deb ... Unpacking python3-pygments (2.18.0+dfsg-1) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../76-python3-urllib3_2.0.7-2_all.deb ... Unpacking python3-urllib3 (2.0.7-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../77-python3-requests_2.32.3+dfsg-1_all.deb ... Unpacking python3-requests (2.32.3+dfsg-1) ... Selecting previously unselected package python3-snowballstemmer. Preparing to unpack .../78-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../79-sphinx-common_7.4.7-4_all.deb ... Unpacking sphinx-common (7.4.7-4) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../80-python3-sphinx_7.4.7-4_all.deb ... Unpacking python3-sphinx (7.4.7-4) ... Selecting previously unselected package sphinx-rtd-theme-common. Preparing to unpack .../81-sphinx-rtd-theme-common_3.0.2+dfsg-1_all.deb ... Unpacking sphinx-rtd-theme-common (3.0.2+dfsg-1) ... Selecting previously unselected package python3-sphinxcontrib.jquery. Preparing to unpack .../82-python3-sphinxcontrib.jquery_4.1-5_all.deb ... Unpacking python3-sphinxcontrib.jquery (4.1-5) ... Selecting previously unselected package python3-sphinx-rtd-theme. Preparing to unpack .../83-python3-sphinx-rtd-theme_3.0.2+dfsg-1_all.deb ... Unpacking python3-sphinx-rtd-theme (3.0.2+dfsg-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.8-1) ... Setting up libkeyutils1:arm64 (1.6.3-4) ... Setting up fonts-lato (2.015-1) ... Setting up libicu72:arm64 (72.1-5+b1) ... Setting up bsdextrautils (2.40.2-11) ... Setting up libmagic-mgc (1:5.45-3+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libtirpc-common (1.3.4+ds-1.3) ... Setting up libdebhelper-perl (13.20) ... Setting up libmagic1t64:arm64 (1:5.45-3+b1) ... Setting up gettext-base (0.22.5-2) ... Setting up m4 (1.4.19-4) ... Setting up libcom-err2:arm64 (1.47.1-1+b1) ... Setting up file (1:5.45-3+b1) ... Setting up libelf1t64:arm64 (0.192-4) ... Setting up python-babel-localedata (2.16.0-1) ... Setting up libkrb5support0:arm64 (1.21.3-3) ... Setting up tzdata (2024b-3) ... Current default time zone: 'Etc/UTC' Local time is now: Mon Nov 25 12:52:36 UTC 2024. Universal Time is now: Mon Nov 25 12:52:36 UTC 2024. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up libpython3.13-minimal:arm64 (3.13.0-2) ... Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.22.5-2) ... Setting up libk5crypto3:arm64 (1.21.3-3) ... Setting up autoconf (2.72-3) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libuchardet0:arm64 (0.0.8-1+b2) ... Setting up libjson-perl (4.10000-1) ... Setting up python3.13-minimal (3.13.0-2) ... Setting up netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up libkrb5-3:arm64 (1.21.3-3) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up openssl (3.3.2-2) ... Setting up readline-common (8.2-5) ... Setting up libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Setting up fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Setting up sphinx-rtd-theme-common (3.0.2+dfsg-1) ... Setting up libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... 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.14.0-1) ... Setting up gettext (0.22.5-2) ... Setting up libtool (2.4.7-8) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 146 added, 0 removed; done. Setting up libgssapi-krb5-2:arm64 (1.21.3-3) ... Setting up libjs-sphinxdoc (7.4.7-4) ... Setting up libreadline8t64:arm64 (8.2-5) ... Setting up dh-strip-nondeterminism (1.14.0-1) ... Setting up groff-base (1.23.0-5) ... Setting up xml-core (0.19) ... Setting up libpython3.13-stdlib:arm64 (3.13.0-2) ... Setting up libtirpc3t64:arm64 (1.3.4+ds-1.3+b1) ... Setting up python3.13 (3.13.0-2) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up man-db (2.13.0-1) ... Not building database; man-db/auto-update is not 'true'. Setting up sphinx-common (7.4.7-4) ... Setting up libnsl2:arm64 (1.3.0-3+b3) ... Setting up libpython3.12-stdlib:arm64 (3.12.7-3) ... Setting up python3.12 (3.12.7-3) ... Setting up debhelper (13.20) ... Setting up libpython3-stdlib:arm64 (3.12.7-1) ... Setting up python3 (3.12.7-1) ... Setting up python3-zipp (3.21.0-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up python3-markupsafe (2.1.5-1+b3) ... Setting up python3-roman (4.2-1) ... Setting up python3-jinja2 (3.1.3-1) ... Setting up python3-packaging (24.2-1) ... Setting up python3-sqlparse (0.5.2-1) ... Setting up python3-certifi (2024.8.30+dfsg-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up python3-idna (3.8-2) ... Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-urllib3 (2.0.7-2) ... Setting up python3-asgiref (3.8.1-1) ... Setting up python3-imagesize (1.4.1-1) ... Setting up python3-more-itertools (10.5.0-1) ... Setting up python3-confusable-homoglyphs (3.3.1-1) ... Setting up python3-django (3:4.2.16-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-defusedxml (0.7.1-2) ... Setting up python3-charset-normalizer (3.4.0-1+b1) ... Setting up python3-alabaster (0.7.16-0.1) ... Setting up python3-typeguard (4.4.1-1) ... Setting up python3-all (3.12.7-1) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-jaraco.text (4.0.0-1) ... Setting up python3-pkg-resources (75.2.0-1) ... Setting up python3-setuptools (75.2.0-1) ... Setting up python3-babel (2.16.0-1) ... update-alternatives: using /usr/bin/pybabel-python3 to provide /usr/bin/pybabel (pybabel) in auto mode Setting up python3-pygments (2.18.0+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-requests (2.32.3+dfsg-1) ... Setting up dh-python (6.20241024) ... Processing triggers for libc-bin (2.40-4) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.21.2+dfsg-2) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.21.2+dfsg-2) ... Setting up python3-sphinx (7.4.7-4) ... Setting up python3-sphinxcontrib.jquery (4.1-5) ... Setting up python3-sphinx-rtd-theme (3.0.2+dfsg-1) ... Processing triggers for ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. 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/python-django-registration-3.3/ && 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 > ../python-django-registration_3.3-1_source.changes dpkg-buildpackage: info: source package python-django-registration dpkg-buildpackage: info: source version 3.3-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Elena Grandi dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --with python3,sphinxdoc --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' rm -rf docs/_build/ dh_auto_clean I: pybuild base:311: python3.13 setup.py clean running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it I: pybuild base:311: python3.12 setup.py clean running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config running config I: pybuild base:311: python3.12 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' cd src/django_registration && /usr/bin/django-admin compilemessages processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fr/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nb/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/da/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/tr_TR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/de/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt_BR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/it/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/is/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_TW/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/en/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ca/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_CN/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/he/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/el/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sr/LC_MESSAGES/django.po” is already compiled and up to date. processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ar/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es_AR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/hr/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date. cd docs && /usr/bin/make html make[2]: Entering directory '/build/reproducible-path/python-django-registration-3.3/docs' sphinx-build -b html -d _build/doctrees . _build/html Running Sphinx v7.4.7 WARNING: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code. loading translations [en]... done making output directory... done Converting `source_suffix = '.rst'` to `source_suffix = {'.rst': 'restructuredtext'}`. loading intersphinx inventory 'django' from https://docs.djangoproject.com/en/stable/_objects/... loading intersphinx inventory 'python' from https://docs.python.org/3/objects.inv... WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.djangoproject.com/en/stable/_objects/' not fetchable due to : HTTPSConnectionPool(host='docs.djangoproject.com', port=443): Max retries exceeded with url: /en/stable/_objects/ (Caused by NameResolutionError(": Failed to resolve 'docs.djangoproject.com' ([Errno -3] Temporary failure in name resolution)")) WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.python.org' ([Errno -3] Temporary failure in name resolution)")) building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 16 source files that are out of date updating environment: [new config] 16 added, 0 changed, 0 removed reading sources... [ 6%] activation-workflow reading sources... [ 12%] custom-user reading sources... [ 19%] deprecations reading sources... [ 25%] exceptions reading sources... [ 31%] faq reading sources... [ 38%] forms reading sources... [ 44%] index reading sources... [ 50%] install reading sources... [ 56%] one-step-workflow reading sources... [ 62%] quickstart reading sources... [ 69%] security reading sources... [ 75%] settings reading sources... [ 81%] signals reading sources... [ 88%] upgrade reading sources... [ 94%] validators reading sources... [100%] views looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done copying assets... copying static files... done copying extra files... done copying assets: done writing output... [ 6%] activation-workflow writing output... [ 12%] custom-user writing output... [ 19%] deprecations writing output... [ 25%] exceptions writing output... [ 31%] faq writing output... [ 38%] forms writing output... [ 44%] index writing output... [ 50%] install writing output... [ 56%] one-step-workflow writing output... [ 62%] quickstart writing output... [ 69%] security writing output... [ 75%] settings writing output... [ 81%] signals writing output... [ 88%] upgrade writing output... [ 94%] validators writing output... [100%] views generating indices... genindex py-modindex done writing additional pages... search done dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 3 warnings. The HTML pages are in _build/html. Build finished. The HTML pages are in _build/html. make[2]: Leaving directory '/build/reproducible-path/python-django-registration-3.3/docs' dh_auto_build I: pybuild base:311: /usr/bin/python3.13 setup.py build running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation running egg_info creating src/django_registration.egg-info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt writing manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation running egg_info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.13 /build/reproducible-path/python-django-registration-3.3/runtests.py Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Found 73 test(s). Operations to perform: Apply all migrations: auth, contenttypes, django_registration, sessions, sites, tests Running migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_registration.0001_initial... OK Applying sessions.0001_initial... OK Applying sites.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Applying tests.0001_initial... OK System check identified no issues (0 silenced). test_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_bad_key) An invalid activation key fails to activate. ... ok test_custom_user_configured (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendViewTests.test_bad_key) An invalid activation key fails to activate. ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendViewTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_registration (tests.base.ActivationTestCase.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.base.ActivationTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.ActivationTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.ActivationTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.base.ActivationTestCase.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.base.ActivationTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.ActivationTestCase.test_registration_signal) ... ok test_case_insensitive_form (tests.test_forms.RegistrationFormTests.test_case_insensitive_form) Test the case-insensitive registration form. ... ok test_case_insensitive_validator (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator) Test the case-insensitive username validator. ... ok test_case_insensitive_validator_eq (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator_eq) Test CaseInsensitiveUnique __eq__ method. ... ok test_confusable_emails (tests.test_forms.RegistrationFormTests.test_confusable_emails) Usernames containing dangerously confusable use of Unicode are ... ok test_confusable_usernames (tests.test_forms.RegistrationFormTests.test_confusable_usernames) Usernames containing dangerously confusable use of Unicode are ... ok test_confusables_email_validator (tests.test_forms.RegistrationFormTests.test_confusables_email_validator) Test the confusable-email validator standalone. ... ok test_confusables_validator (tests.test_forms.RegistrationFormTests.test_confusables_validator) Test the confusable-username validator standalone. ... ok test_custom_reserved_names (tests.test_forms.RegistrationFormTests.test_custom_reserved_names) Reserved names can be overridden by an attribute. ... ok test_email_required (tests.test_forms.RegistrationFormTests.test_email_required) The email address field is required. ... ok test_email_uniqueness (tests.test_forms.RegistrationFormTests.test_email_uniqueness) Email uniqueness is enforced by RegistrationFormUniqueEmail. ... ok test_email_validation (tests.test_forms.RegistrationFormTests.test_email_validation) Stricter-than-RFC email validation is applied. ... ok test_email_validator (tests.test_forms.RegistrationFormTests.test_email_validator) Test the HTMl5 email address validator. ... ok test_reserved_name_non_string (tests.test_forms.RegistrationFormTests.test_reserved_name_non_string) GitHub issue #82: reserved-name validator should not attempt ... ok test_reserved_name_validator_eq (tests.test_forms.RegistrationFormTests.test_reserved_name_validator_eq) Test ReservedNameValidator __eq__ method. ... ok test_reserved_names (tests.test_forms.RegistrationFormTests.test_reserved_names) Reserved names are disallowed. ... ok test_tos_field (tests.test_forms.RegistrationFormTests.test_tos_field) The terms-of-service field on RegistrationFormTermsOfService ... ok test_username_uniqueness (tests.test_forms.RegistrationFormTests.test_username_uniqueness) Username uniqueness is enforced. ... ok test_custom_user_configured (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_signal) ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_signal) ... ok test_registration (tests.base.WorkflowTestCase.test_registration) Registration creates a new account. ... ok test_registration_closed (tests.base.WorkflowTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.WorkflowTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.WorkflowTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.base.WorkflowTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.WorkflowTestCase.test_registration_signal) ... ok test_activation (tests.test_views.ActivationViewTests.test_activation) Activation of an account functions properly when using a ... ok test_user_mismatch_breaks_view (tests.test_views.CustomUserTests.test_user_mismatch_breaks_view) When RegistrationView detects a mismatch between the model used by ... ok test_sensitive_post_parameters_are_filtered (tests.test_views.SensitiveParameterFilterTests.test_sensitive_post_parameters_are_filtered) When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- Ran 73 tests in 10.188s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... I: pybuild base:311: cd /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.12 /build/reproducible-path/python-django-registration-3.3/runtests.py Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Found 73 test(s). Operations to perform: Apply all migrations: auth, contenttypes, django_registration, sessions, sites, tests Running migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_registration.0001_initial... OK Applying sessions.0001_initial... OK Applying sites.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Applying tests.0001_initial... OK System check identified no issues (0 silenced). test_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_bad_key) An invalid activation key fails to activate. ... ok test_custom_user_configured (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendViewTests.test_bad_key) An invalid activation key fails to activate. ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendViewTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_registration (tests.base.ActivationTestCase.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.base.ActivationTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.ActivationTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.ActivationTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.base.ActivationTestCase.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.base.ActivationTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.ActivationTestCase.test_registration_signal) ... ok test_case_insensitive_form (tests.test_forms.RegistrationFormTests.test_case_insensitive_form) Test the case-insensitive registration form. ... ok test_case_insensitive_validator (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator) Test the case-insensitive username validator. ... ok test_case_insensitive_validator_eq (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator_eq) Test CaseInsensitiveUnique __eq__ method. ... ok test_confusable_emails (tests.test_forms.RegistrationFormTests.test_confusable_emails) Usernames containing dangerously confusable use of Unicode are ... ok test_confusable_usernames (tests.test_forms.RegistrationFormTests.test_confusable_usernames) Usernames containing dangerously confusable use of Unicode are ... ok test_confusables_email_validator (tests.test_forms.RegistrationFormTests.test_confusables_email_validator) Test the confusable-email validator standalone. ... ok test_confusables_validator (tests.test_forms.RegistrationFormTests.test_confusables_validator) Test the confusable-username validator standalone. ... ok test_custom_reserved_names (tests.test_forms.RegistrationFormTests.test_custom_reserved_names) Reserved names can be overridden by an attribute. ... ok test_email_required (tests.test_forms.RegistrationFormTests.test_email_required) The email address field is required. ... ok test_email_uniqueness (tests.test_forms.RegistrationFormTests.test_email_uniqueness) Email uniqueness is enforced by RegistrationFormUniqueEmail. ... ok test_email_validation (tests.test_forms.RegistrationFormTests.test_email_validation) Stricter-than-RFC email validation is applied. ... ok test_email_validator (tests.test_forms.RegistrationFormTests.test_email_validator) Test the HTMl5 email address validator. ... ok test_reserved_name_non_string (tests.test_forms.RegistrationFormTests.test_reserved_name_non_string) GitHub issue #82: reserved-name validator should not attempt ... ok test_reserved_name_validator_eq (tests.test_forms.RegistrationFormTests.test_reserved_name_validator_eq) Test ReservedNameValidator __eq__ method. ... ok test_reserved_names (tests.test_forms.RegistrationFormTests.test_reserved_names) Reserved names are disallowed. ... ok test_tos_field (tests.test_forms.RegistrationFormTests.test_tos_field) The terms-of-service field on RegistrationFormTermsOfService ... ok test_username_uniqueness (tests.test_forms.RegistrationFormTests.test_username_uniqueness) Username uniqueness is enforced. ... ok test_custom_user_configured (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_signal) ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_signal) ... ok test_registration (tests.base.WorkflowTestCase.test_registration) Registration creates a new account. ... ok test_registration_closed (tests.base.WorkflowTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.WorkflowTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.WorkflowTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.base.WorkflowTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.WorkflowTestCase.test_registration_signal) ... ok test_activation (tests.test_views.ActivationViewTests.test_activation) Activation of an account functions properly when using a ... ok test_user_mismatch_breaks_view (tests.test_views.CustomUserTests.test_user_mismatch_breaks_view) When RegistrationView detects a mismatch between the model used by ... ok test_sensitive_post_parameters_are_filtered (tests.test_views.SensitiveParameterFilterTests.test_sensitive_post_parameters_are_filtered) When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- Ran 73 tests in 10.306s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild debian/rules override_dh_auto_install make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' # dh_auto_install expects the following directory to exist (before it # is created?) mkdir -p debian/python-django-registration-doc dh_auto_install I: pybuild base:311: /usr/bin/python3.13 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration 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 src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.__pycache__' to be distributed and are already explicitly excluding 'django_registration.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.activation.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.activation.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.activation.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.activation.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.activation.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.one_step.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.one_step.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.one_step.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.one_step.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.one_step.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.migrations.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.migrations.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.migrations.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.migrations.__pycache__' to be distributed and are already explicitly excluding 'django_registration.migrations.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/views.py to views.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/views.py to views.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/exceptions.py to exceptions.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/forms.py to forms.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/signals.py to signals.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/validators.py to validators.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/views.py to views.cpython-313.pyc running install_egg_info Copying src/django_registration.egg-info to /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration-3.3.egg-info Skipping SOURCES.txt running install_scripts I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration 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 src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.__pycache__' to be distributed and are already explicitly excluding 'django_registration.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.activation.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.activation.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.activation.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.activation.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.activation.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.one_step.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.one_step.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.one_step.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.one_step.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.one_step.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.migrations.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.migrations.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.migrations.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.migrations.__pycache__' to be distributed and are already explicitly excluding 'django_registration.migrations.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/exceptions.py to exceptions.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/forms.py to forms.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/signals.py to signals.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/validators.py to validators.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/views.py to views.cpython-312.pyc running install_egg_info Copying src/django_registration.egg-info to /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration-3.3.egg-info Skipping SOURCES.txt running install_scripts # Drop .po files and keep only .mo files (compiled) find debian/python3-django-registration/ -name '*.po' -exec rm -v {} \; ; find debian/python-django-registration-doc/ -name '*.po' -exec rm -v {} \; ; removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_installdocs -O--buildsystem=pybuild dh_installdocs: warning: Cannot auto-detect main package for python-django-registration-doc. If the default is wrong, please use --doc-main-package dh_sphinxdoc -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 Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/it/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/is/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/he/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/en/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/el/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/de/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/da/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.mo 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 dpkg-gencontrol: warning: package python-django-registration-doc: substitution variable ${sphinxdoc:Built-Using} unused, but is defined dpkg-gencontrol: warning: Depends field of package python3-django-registration: substitution variable ${sphinxdoc:Depends} used, but is not defined dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-django-registration' in '../python3-django-registration_3.3-1_all.deb'. dpkg-deb: building package 'python-django-registration-doc' in '../python-django-registration-doc_3.3-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python-django-registration_3.3-1_arm64.buildinfo dpkg-genchanges --build=binary -O../python-django-registration_3.3-1_arm64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /srv/workspace/pbuilder/3825326 and its subdirectories I: Current time: Mon Nov 25 00:53:46 -12 2024 I: pbuilder-time-stamp: 1732539226 Mon Nov 25 12:53:46 UTC 2024 I: Signing ./b1/python-django-registration_3.3-1_arm64.buildinfo as python-django-registration_3.3-1_arm64.buildinfo.asc Mon Nov 25 12:53:46 UTC 2024 I: Signed ./b1/python-django-registration_3.3-1_arm64.buildinfo as ./b1/python-django-registration_3.3-1_arm64.buildinfo.asc Mon Nov 25 12:53:46 UTC 2024 - build #1 for python-django-registration/unstable/arm64 on codethink02-arm64 done. Starting cleanup. All cleanup done. Mon Nov 25 12:53:46 UTC 2024 - reproducible_build.sh stopped running as /tmp/jenkins-script-VXvkTbYo, removing. /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy: total 16 drwxr-xr-x 2 jenkins jenkins 4096 Nov 25 12:53 b1 drwxr-xr-x 2 jenkins jenkins 4096 Nov 25 12:52 b2 -rw-r--r-- 1 jenkins jenkins 2355 Oct 24 2022 python-django-registration_3.3-1.dsc -rw------- 1 jenkins jenkins 3589 Nov 25 12:52 rbuildlog.zwAjPsW /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1: total 752 -rw-r--r-- 1 jenkins jenkins 539765 Nov 25 12:53 build.log -rw-r--r-- 1 jenkins jenkins 64268 Nov 25 12:53 python-django-registration-doc_3.3-1_all.deb -rw-r--r-- 1 jenkins jenkins 10396 Nov 25 12:53 python-django-registration_3.3-1.debian.tar.xz -rw-r--r-- 1 jenkins jenkins 2355 Nov 25 12:53 python-django-registration_3.3-1.dsc -rw-r--r-- 1 jenkins jenkins 7649 Nov 25 12:53 python-django-registration_3.3-1_arm64.buildinfo -rw-r--r-- 1 jenkins jenkins 8531 Nov 25 12:53 python-django-registration_3.3-1_arm64.buildinfo.asc -rw-r--r-- 1 jenkins jenkins 2047 Nov 25 12:53 python-django-registration_3.3-1_arm64.changes -rw-r--r-- 1 jenkins jenkins 2403 Nov 25 12:53 python-django-registration_3.3-1_source.changes -rw-r--r-- 1 jenkins jenkins 85046 Nov 25 12:53 python-django-registration_3.3.orig.tar.gz -rw-r--r-- 1 jenkins jenkins 833 Nov 25 12:53 python-django-registration_3.3.orig.tar.gz.asc -rw-r--r-- 1 jenkins jenkins 26504 Nov 25 12:53 python3-django-registration_3.3-1_all.deb /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2: total 0 Mon Nov 25 12:53:47 UTC 2024 I: Deleting $TMPDIR on codethink02-arm64.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Mon Nov 25 00:52:15 -12 2024 I: pbuilder-time-stamp: 1732539135 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Copying source file I: copying [python-django-registration_3.3-1.dsc] I: copying [./python-django-registration_3.3.orig.tar.gz] I: copying [./python-django-registration_3.3.orig.tar.gz.asc] I: copying [./python-django-registration_3.3-1.debian.tar.xz] I: Extracting source gpgv: Signature made Mon Oct 24 11:37:05 2022 gpgv: using RSA key 63C9FAAC68393E94CF925E1970BD22D31123B431 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./python-django-registration_3.3-1.dsc: no acceptable signature found dpkg-source: info: extracting python-django-registration in python-django-registration-3.3 dpkg-source: info: unpacking python-django-registration_3.3.orig.tar.gz dpkg-source: info: unpacking python-django-registration_3.3-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/3825326/tmp/hooks/D02_print_environment starting I: set BUILDDIR='/build/reproducible-path' BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' BUILDUSERNAME='pbuilder1' BUILD_ARCH='arm64' DEBIAN_FRONTEND='noninteractive' DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' DISTRIBUTION='unstable' HOME='/root' HOST_ARCH='arm64' IFS=' ' INVOCATION_ID='0e0b7970444f480989ce537bf542d0e0' LANG='C' LANGUAGE='en_US:en' LC_ALL='C' MAIL='/var/mail/root' OPTIND='1' PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' PBCURRENTCOMMANDLINEOPERATION='build' PBUILDER_OPERATION='build' PBUILDER_PKGDATADIR='/usr/share/pbuilder' PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' PBUILDER_SYSCONFDIR='/etc' PPID='3825326' 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.SUQ9kGBy/pbuilderrc_acZp --distribution unstable --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1 --logfile b1/build.log python-django-registration_3.3-1.dsc' SUDO_GID='109' SUDO_UID='104' SUDO_USER='jenkins' TERM='unknown' TZ='/usr/share/zoneinfo/Etc/GMT+12' USER='root' _='/usr/bin/systemd-run' http_proxy='http://192.168.101.4:3128' I: uname -a Linux codethink02-arm64 6.1.0-28-cloud-arm64 #1 SMP Debian 6.1.119-1 (2024-11-22) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Nov 22 14:40 /bin -> usr/bin I: user script /srv/workspace/pbuilder/3825326/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: arm64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper-compat (= 13), dh-python, python3-all, python3-setuptools, python3-confusable-homoglyphs (>= 3), python3-django, python3-sphinx, python3-sphinx-rtd-theme dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20083 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-all; however: Package python3-all is not installed. pbuilder-satisfydepends-dummy depends on python3-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3-confusable-homoglyphs (>= 3); however: Package python3-confusable-homoglyphs is not installed. pbuilder-satisfydepends-dummy depends on python3-django; however: Package python3-django is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx; however: Package python3-sphinx is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx-rtd-theme; however: Package python3-sphinx-rtd-theme 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} ca-certificates{a} debhelper{a} dh-autoreconf{a} dh-python{a} dh-strip-nondeterminism{a} docutils-common{a} dwz{a} file{a} fonts-font-awesome{a} fonts-lato{a} gettext{a} gettext-base{a} groff-base{a} intltool-debian{a} libarchive-zip-perl{a} libcom-err2{a} libdebhelper-perl{a} libelf1t64{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libgssapi-krb5-2{a} libicu72{a} libjs-jquery{a} libjs-sphinxdoc{a} libjs-underscore{a} libjson-perl{a} libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} libmagic-mgc{a} libmagic1t64{a} libnsl2{a} libpipeline1{a} libpython3-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libpython3.13-minimal{a} libpython3.13-stdlib{a} libreadline8t64{a} libtirpc-common{a} libtirpc3t64{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} po-debconf{a} python-babel-localedata{a} python3{a} python3-alabaster{a} python3-all{a} python3-asgiref{a} python3-autocommand{a} python3-babel{a} python3-certifi{a} python3-chardet{a} python3-charset-normalizer{a} python3-confusable-homoglyphs{a} python3-defusedxml{a} python3-django{a} python3-docutils{a} python3-idna{a} python3-imagesize{a} python3-inflect{a} python3-jaraco.context{a} python3-jaraco.functools{a} python3-jaraco.text{a} python3-jinja2{a} python3-markupsafe{a} python3-minimal{a} python3-more-itertools{a} python3-packaging{a} python3-pkg-resources{a} python3-pygments{a} python3-requests{a} python3-roman{a} python3-setuptools{a} python3-snowballstemmer{a} python3-sphinx{a} python3-sphinx-rtd-theme{a} python3-sphinxcontrib.jquery{a} python3-sqlparse{a} python3-typeguard{a} python3-typing-extensions{a} python3-urllib3{a} python3-zipp{a} python3.12{a} python3.12-minimal{a} python3.13{a} python3.13-minimal{a} readline-common{a} sensible-utils{a} sgml-base{a} sphinx-common{a} sphinx-rtd-theme-common{a} tzdata{a} xml-core{a} The following packages are RECOMMENDED but will NOT be installed: curl javascript-common krb5-locales libarchive-cpio-perl libjson-xs-perl libltdl-dev libmail-sendmail-perl libpaper-utils lynx python3-click python3-pil python3-tz wget 0 packages upgraded, 106 newly installed, 0 to remove and 0 not upgraded. Need to get 51.6 MB of archives. After unpacking 234 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian unstable/main arm64 fonts-lato all 2.015-1 [2780 kB] Get: 2 http://deb.debian.org/debian unstable/main arm64 libpython3.12-minimal arm64 3.12.7-3 [808 kB] Get: 3 http://deb.debian.org/debian unstable/main arm64 libexpat1 arm64 2.6.4-1 [90.7 kB] Get: 4 http://deb.debian.org/debian unstable/main arm64 python3.12-minimal arm64 3.12.7-3 [1940 kB] Get: 5 http://deb.debian.org/debian unstable/main arm64 python3-minimal arm64 3.12.7-1 [26.8 kB] Get: 6 http://deb.debian.org/debian unstable/main arm64 media-types all 10.1.0 [26.9 kB] Get: 7 http://deb.debian.org/debian unstable/main arm64 netbase all 6.4 [12.8 kB] Get: 8 http://deb.debian.org/debian unstable/main arm64 tzdata all 2024b-3 [255 kB] Get: 9 http://deb.debian.org/debian unstable/main arm64 libkrb5support0 arm64 1.21.3-3 [32.1 kB] Get: 10 http://deb.debian.org/debian unstable/main arm64 libcom-err2 arm64 1.47.1-1+b1 [23.1 kB] Get: 11 http://deb.debian.org/debian unstable/main arm64 libk5crypto3 arm64 1.21.3-3 [80.8 kB] Get: 12 http://deb.debian.org/debian unstable/main arm64 libkeyutils1 arm64 1.6.3-4 [9352 B] Get: 13 http://deb.debian.org/debian unstable/main arm64 libkrb5-3 arm64 1.21.3-3 [310 kB] Get: 14 http://deb.debian.org/debian unstable/main arm64 libgssapi-krb5-2 arm64 1.21.3-3 [126 kB] Get: 15 http://deb.debian.org/debian unstable/main arm64 libtirpc-common all 1.3.4+ds-1.3 [10.9 kB] Get: 16 http://deb.debian.org/debian unstable/main arm64 libtirpc3t64 arm64 1.3.4+ds-1.3+b1 [78.7 kB] Get: 17 http://deb.debian.org/debian unstable/main arm64 libnsl2 arm64 1.3.0-3+b3 [37.9 kB] Get: 18 http://deb.debian.org/debian unstable/main arm64 readline-common all 8.2-5 [69.3 kB] Get: 19 http://deb.debian.org/debian unstable/main arm64 libreadline8t64 arm64 8.2-5 [159 kB] Get: 20 http://deb.debian.org/debian unstable/main arm64 libpython3.12-stdlib arm64 3.12.7-3 [1902 kB] Get: 21 http://deb.debian.org/debian unstable/main arm64 python3.12 arm64 3.12.7-3 [671 kB] Get: 22 http://deb.debian.org/debian unstable/main arm64 libpython3-stdlib arm64 3.12.7-1 [9708 B] Get: 23 http://deb.debian.org/debian unstable/main arm64 python3 arm64 3.12.7-1 [27.8 kB] Get: 24 http://deb.debian.org/debian unstable/main arm64 libpython3.13-minimal arm64 3.13.0-2 [850 kB] Get: 25 http://deb.debian.org/debian unstable/main arm64 python3.13-minimal arm64 3.13.0-2 [1838 kB] Get: 26 http://deb.debian.org/debian unstable/main arm64 sgml-base all 1.31 [15.4 kB] Get: 27 http://deb.debian.org/debian unstable/main arm64 sensible-utils all 0.0.24 [24.8 kB] Get: 28 http://deb.debian.org/debian unstable/main arm64 openssl arm64 3.3.2-2 [1347 kB] Get: 29 http://deb.debian.org/debian unstable/main arm64 ca-certificates all 20240203 [158 kB] Get: 30 http://deb.debian.org/debian unstable/main arm64 libmagic-mgc arm64 1:5.45-3+b1 [314 kB] Get: 31 http://deb.debian.org/debian unstable/main arm64 libmagic1t64 arm64 1:5.45-3+b1 [102 kB] Get: 32 http://deb.debian.org/debian unstable/main arm64 file arm64 1:5.45-3+b1 [43.4 kB] Get: 33 http://deb.debian.org/debian unstable/main arm64 gettext-base arm64 0.22.5-2 [198 kB] Get: 34 http://deb.debian.org/debian unstable/main arm64 libuchardet0 arm64 0.0.8-1+b2 [69.2 kB] Get: 35 http://deb.debian.org/debian unstable/main arm64 groff-base arm64 1.23.0-5 [1129 kB] Get: 36 http://deb.debian.org/debian unstable/main arm64 bsdextrautils arm64 2.40.2-11 [91.2 kB] Get: 37 http://deb.debian.org/debian unstable/main arm64 libpipeline1 arm64 1.5.8-1 [40.2 kB] Get: 38 http://deb.debian.org/debian unstable/main arm64 man-db arm64 2.13.0-1 [1404 kB] Get: 39 http://deb.debian.org/debian unstable/main arm64 m4 arm64 1.4.19-4 [277 kB] Get: 40 http://deb.debian.org/debian unstable/main arm64 autoconf all 2.72-3 [493 kB] Get: 41 http://deb.debian.org/debian unstable/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 42 http://deb.debian.org/debian unstable/main arm64 automake all 1:1.16.5-1.3 [823 kB] Get: 43 http://deb.debian.org/debian unstable/main arm64 autopoint all 0.22.5-2 [723 kB] Get: 44 http://deb.debian.org/debian unstable/main arm64 libdebhelper-perl all 13.20 [89.7 kB] Get: 45 http://deb.debian.org/debian unstable/main arm64 libtool all 2.4.7-8 [517 kB] Get: 46 http://deb.debian.org/debian unstable/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 47 http://deb.debian.org/debian unstable/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 48 http://deb.debian.org/debian unstable/main arm64 libfile-stripnondeterminism-perl all 1.14.0-1 [19.5 kB] Get: 49 http://deb.debian.org/debian unstable/main arm64 dh-strip-nondeterminism all 1.14.0-1 [8448 B] Get: 50 http://deb.debian.org/debian unstable/main arm64 libelf1t64 arm64 0.192-4 [189 kB] Get: 51 http://deb.debian.org/debian unstable/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 52 http://deb.debian.org/debian unstable/main arm64 libicu72 arm64 72.1-5+b1 [9239 kB] Get: 53 http://deb.debian.org/debian unstable/main arm64 libxml2 arm64 2.12.7+dfsg+really2.9.14-0.2+b1 [630 kB] Get: 54 http://deb.debian.org/debian unstable/main arm64 gettext arm64 0.22.5-2 [1532 kB] Get: 55 http://deb.debian.org/debian unstable/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 56 http://deb.debian.org/debian unstable/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 57 http://deb.debian.org/debian unstable/main arm64 debhelper all 13.20 [915 kB] Get: 58 http://deb.debian.org/debian unstable/main arm64 python3-autocommand all 2.2.2-3 [13.6 kB] Get: 59 http://deb.debian.org/debian unstable/main arm64 python3-more-itertools all 10.5.0-1 [63.8 kB] Get: 60 http://deb.debian.org/debian unstable/main arm64 python3-typing-extensions all 4.12.2-2 [73.0 kB] Get: 61 http://deb.debian.org/debian unstable/main arm64 python3-typeguard all 4.4.1-1 [37.0 kB] Get: 62 http://deb.debian.org/debian unstable/main arm64 python3-inflect all 7.3.1-2 [32.4 kB] Get: 63 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.context all 6.0.0-1 [7984 B] Get: 64 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.functools all 4.1.0-1 [12.0 kB] Get: 65 http://deb.debian.org/debian unstable/main arm64 python3-pkg-resources all 75.2.0-1 [213 kB] Get: 66 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.text all 4.0.0-1 [11.4 kB] Get: 67 http://deb.debian.org/debian unstable/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 68 http://deb.debian.org/debian unstable/main arm64 python3-setuptools all 75.2.0-1 [731 kB] Get: 69 http://deb.debian.org/debian unstable/main arm64 dh-python all 6.20241024 [109 kB] Get: 70 http://deb.debian.org/debian unstable/main arm64 xml-core all 0.19 [20.1 kB] Get: 71 http://deb.debian.org/debian unstable/main arm64 docutils-common all 0.21.2+dfsg-2 [128 kB] Get: 72 http://deb.debian.org/debian unstable/main arm64 fonts-font-awesome all 5.0.10+really4.7.0~dfsg-4.1 [517 kB] Get: 73 http://deb.debian.org/debian unstable/main arm64 libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get: 74 http://deb.debian.org/debian unstable/main arm64 libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get: 75 http://deb.debian.org/debian unstable/main arm64 libjs-sphinxdoc all 7.4.7-4 [158 kB] Get: 76 http://deb.debian.org/debian unstable/main arm64 libjson-perl all 4.10000-1 [87.5 kB] Get: 77 http://deb.debian.org/debian unstable/main arm64 libpython3.13-stdlib arm64 3.13.0-2 [1922 kB] Get: 78 http://deb.debian.org/debian unstable/main arm64 python-babel-localedata all 2.16.0-1 [5696 kB] Get: 79 http://deb.debian.org/debian unstable/main arm64 python3-alabaster all 0.7.16-0.1 [27.9 kB] Get: 80 http://deb.debian.org/debian unstable/main arm64 python3.13 arm64 3.13.0-2 [730 kB] Get: 81 http://deb.debian.org/debian unstable/main arm64 python3-all arm64 3.12.7-1 [1052 B] Get: 82 http://deb.debian.org/debian unstable/main arm64 python3-asgiref all 3.8.1-1 [28.8 kB] Get: 83 http://deb.debian.org/debian unstable/main arm64 python3-babel all 2.16.0-1 [114 kB] Get: 84 http://deb.debian.org/debian unstable/main arm64 python3-certifi all 2024.8.30+dfsg-1 [9576 B] Get: 85 http://deb.debian.org/debian unstable/main arm64 python3-chardet all 5.2.0+dfsg-1 [107 kB] Get: 86 http://deb.debian.org/debian unstable/main arm64 python3-charset-normalizer arm64 3.4.0-1+b1 [129 kB] Get: 87 http://deb.debian.org/debian unstable/main arm64 python3-confusable-homoglyphs all 3.3.1-1 [128 kB] Get: 88 http://deb.debian.org/debian unstable/main arm64 python3-defusedxml all 0.7.1-2 [43.3 kB] Get: 89 http://deb.debian.org/debian unstable/main arm64 python3-sqlparse all 0.5.2-1 [39.7 kB] Get: 90 http://deb.debian.org/debian unstable/main arm64 python3-django all 3:4.2.16-1 [2738 kB] Get: 91 http://deb.debian.org/debian unstable/main arm64 python3-roman all 4.2-1 [10.4 kB] Get: 92 http://deb.debian.org/debian unstable/main arm64 python3-docutils all 0.21.2+dfsg-2 [403 kB] Get: 93 http://deb.debian.org/debian unstable/main arm64 python3-idna all 3.8-2 [41.6 kB] Get: 94 http://deb.debian.org/debian unstable/main arm64 python3-imagesize all 1.4.1-1 [6688 B] Get: 95 http://deb.debian.org/debian unstable/main arm64 python3-markupsafe arm64 2.1.5-1+b3 [14.0 kB] Get: 96 http://deb.debian.org/debian unstable/main arm64 python3-jinja2 all 3.1.3-1 [119 kB] Get: 97 http://deb.debian.org/debian unstable/main arm64 python3-packaging all 24.2-1 [55.3 kB] Get: 98 http://deb.debian.org/debian unstable/main arm64 python3-pygments all 2.18.0+dfsg-1 [836 kB] Get: 99 http://deb.debian.org/debian unstable/main arm64 python3-urllib3 all 2.0.7-2 [111 kB] Get: 100 http://deb.debian.org/debian unstable/main arm64 python3-requests all 2.32.3+dfsg-1 [71.9 kB] Get: 101 http://deb.debian.org/debian unstable/main arm64 python3-snowballstemmer all 2.2.0-4 [58.0 kB] Get: 102 http://deb.debian.org/debian unstable/main arm64 sphinx-common all 7.4.7-4 [731 kB] Get: 103 http://deb.debian.org/debian unstable/main arm64 python3-sphinx all 7.4.7-4 [588 kB] Get: 104 http://deb.debian.org/debian unstable/main arm64 sphinx-rtd-theme-common all 3.0.2+dfsg-1 [1023 kB] Get: 105 http://deb.debian.org/debian unstable/main arm64 python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 106 http://deb.debian.org/debian unstable/main arm64 python3-sphinx-rtd-theme all 3.0.2+dfsg-1 [29.5 kB] Fetched 51.6 MB in 0s (189 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package fonts-lato. (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 ... 20083 files and directories currently installed.) Preparing to unpack .../fonts-lato_2.015-1_all.deb ... Unpacking fonts-lato (2.015-1) ... Selecting previously unselected package libpython3.12-minimal:arm64. Preparing to unpack .../libpython3.12-minimal_3.12.7-3_arm64.deb ... Unpacking libpython3.12-minimal:arm64 (3.12.7-3) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.4-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.4-1) ... Selecting previously unselected package python3.12-minimal. Preparing to unpack .../python3.12-minimal_3.12.7-3_arm64.deb ... Unpacking python3.12-minimal (3.12.7-3) ... Setting up libpython3.12-minimal:arm64 (3.12.7-3) ... Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.12-minimal (3.12.7-3) ... 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 ... 20429 files and directories currently installed.) Preparing to unpack .../00-python3-minimal_3.12.7-1_arm64.deb ... Unpacking python3-minimal (3.12.7-1) ... Selecting previously unselected package media-types. Preparing to unpack .../01-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../02-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package tzdata. Preparing to unpack .../03-tzdata_2024b-3_all.deb ... Unpacking tzdata (2024b-3) ... Selecting previously unselected package libkrb5support0:arm64. Preparing to unpack .../04-libkrb5support0_1.21.3-3_arm64.deb ... Unpacking libkrb5support0:arm64 (1.21.3-3) ... Selecting previously unselected package libcom-err2:arm64. Preparing to unpack .../05-libcom-err2_1.47.1-1+b1_arm64.deb ... Unpacking libcom-err2:arm64 (1.47.1-1+b1) ... Selecting previously unselected package libk5crypto3:arm64. Preparing to unpack .../06-libk5crypto3_1.21.3-3_arm64.deb ... Unpacking libk5crypto3:arm64 (1.21.3-3) ... Selecting previously unselected package libkeyutils1:arm64. Preparing to unpack .../07-libkeyutils1_1.6.3-4_arm64.deb ... Unpacking libkeyutils1:arm64 (1.6.3-4) ... Selecting previously unselected package libkrb5-3:arm64. Preparing to unpack .../08-libkrb5-3_1.21.3-3_arm64.deb ... Unpacking libkrb5-3:arm64 (1.21.3-3) ... Selecting previously unselected package libgssapi-krb5-2:arm64. Preparing to unpack .../09-libgssapi-krb5-2_1.21.3-3_arm64.deb ... Unpacking libgssapi-krb5-2:arm64 (1.21.3-3) ... Selecting previously unselected package libtirpc-common. Preparing to unpack .../10-libtirpc-common_1.3.4+ds-1.3_all.deb ... Unpacking libtirpc-common (1.3.4+ds-1.3) ... Selecting previously unselected package libtirpc3t64:arm64. Preparing to unpack .../11-libtirpc3t64_1.3.4+ds-1.3+b1_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libtirpc.so.3 to /lib/aarch64-linux-gnu/libtirpc.so.3.usr-is-merged by libtirpc3t64' Adding 'diversion of /lib/aarch64-linux-gnu/libtirpc.so.3.0.0 to /lib/aarch64-linux-gnu/libtirpc.so.3.0.0.usr-is-merged by libtirpc3t64' Unpacking libtirpc3t64:arm64 (1.3.4+ds-1.3+b1) ... Selecting previously unselected package libnsl2:arm64. Preparing to unpack .../12-libnsl2_1.3.0-3+b3_arm64.deb ... Unpacking libnsl2:arm64 (1.3.0-3+b3) ... Selecting previously unselected package readline-common. Preparing to unpack .../13-readline-common_8.2-5_all.deb ... Unpacking readline-common (8.2-5) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../14-libreadline8t64_8.2-5_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8 to /lib/aarch64-linux-gnu/libhistory.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8.2 to /lib/aarch64-linux-gnu/libhistory.so.8.2.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8 to /lib/aarch64-linux-gnu/libreadline.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8.2 to /lib/aarch64-linux-gnu/libreadline.so.8.2.usr-is-merged by libreadline8t64' Unpacking libreadline8t64:arm64 (8.2-5) ... Selecting previously unselected package libpython3.12-stdlib:arm64. Preparing to unpack .../15-libpython3.12-stdlib_3.12.7-3_arm64.deb ... Unpacking libpython3.12-stdlib:arm64 (3.12.7-3) ... Selecting previously unselected package python3.12. Preparing to unpack .../16-python3.12_3.12.7-3_arm64.deb ... Unpacking python3.12 (3.12.7-3) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../17-libpython3-stdlib_3.12.7-1_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.12.7-1) ... Setting up python3-minimal (3.12.7-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 ... 21491 files and directories currently installed.) Preparing to unpack .../00-python3_3.12.7-1_arm64.deb ... Unpacking python3 (3.12.7-1) ... Selecting previously unselected package libpython3.13-minimal:arm64. Preparing to unpack .../01-libpython3.13-minimal_3.13.0-2_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.0-2) ... Selecting previously unselected package python3.13-minimal. Preparing to unpack .../02-python3.13-minimal_3.13.0-2_arm64.deb ... Unpacking python3.13-minimal (3.13.0-2) ... Selecting previously unselected package sgml-base. Preparing to unpack .../03-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../04-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package openssl. Preparing to unpack .../05-openssl_3.3.2-2_arm64.deb ... Unpacking openssl (3.3.2-2) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../06-ca-certificates_20240203_all.deb ... Unpacking ca-certificates (20240203) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../07-libmagic-mgc_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3+b1) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../08-libmagic1t64_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3+b1) ... Selecting previously unselected package file. Preparing to unpack .../09-file_1%3a5.45-3+b1_arm64.deb ... Unpacking file (1:5.45-3+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../10-gettext-base_0.22.5-2_arm64.deb ... Unpacking gettext-base (0.22.5-2) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../11-libuchardet0_0.0.8-1+b2_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b2) ... Selecting previously unselected package groff-base. Preparing to unpack .../12-groff-base_1.23.0-5_arm64.deb ... Unpacking groff-base (1.23.0-5) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../13-bsdextrautils_2.40.2-11_arm64.deb ... Unpacking bsdextrautils (2.40.2-11) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../14-libpipeline1_1.5.8-1_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../15-man-db_2.13.0-1_arm64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../16-m4_1.4.19-4_arm64.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../17-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../18-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../19-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 .../20-autopoint_0.22.5-2_all.deb ... Unpacking autopoint (0.22.5-2) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../21-libdebhelper-perl_13.20_all.deb ... Unpacking libdebhelper-perl (13.20) ... Selecting previously unselected package libtool. Preparing to unpack .../22-libtool_2.4.7-8_all.deb ... Unpacking libtool (2.4.7-8) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../23-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../24-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../25-libfile-stripnondeterminism-perl_1.14.0-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.0-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../26-dh-strip-nondeterminism_1.14.0-1_all.deb ... Unpacking dh-strip-nondeterminism (1.14.0-1) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../27-libelf1t64_0.192-4_arm64.deb ... Unpacking libelf1t64:arm64 (0.192-4) ... Selecting previously unselected package dwz. Preparing to unpack .../28-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../29-libicu72_72.1-5+b1_arm64.deb ... Unpacking libicu72:arm64 (72.1-5+b1) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../30-libxml2_2.12.7+dfsg+really2.9.14-0.2+b1_arm64.deb ... Unpacking libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Selecting previously unselected package gettext. Preparing to unpack .../31-gettext_0.22.5-2_arm64.deb ... Unpacking gettext (0.22.5-2) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../32-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 .../33-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../34-debhelper_13.20_all.deb ... Unpacking debhelper (13.20) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../35-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../36-python3-more-itertools_10.5.0-1_all.deb ... Unpacking python3-more-itertools (10.5.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../37-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../38-python3-typeguard_4.4.1-1_all.deb ... Unpacking python3-typeguard (4.4.1-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../39-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../40-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../41-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../42-python3-pkg-resources_75.2.0-1_all.deb ... Unpacking python3-pkg-resources (75.2.0-1) ... Selecting previously unselected package python3-jaraco.text. Preparing to unpack .../43-python3-jaraco.text_4.0.0-1_all.deb ... Unpacking python3-jaraco.text (4.0.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../44-python3-zipp_3.21.0-1_all.deb ... Unpacking python3-zipp (3.21.0-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../45-python3-setuptools_75.2.0-1_all.deb ... Unpacking python3-setuptools (75.2.0-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../46-dh-python_6.20241024_all.deb ... Unpacking dh-python (6.20241024) ... Selecting previously unselected package xml-core. Preparing to unpack .../47-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../48-docutils-common_0.21.2+dfsg-2_all.deb ... Unpacking docutils-common (0.21.2+dfsg-2) ... Selecting previously unselected package fonts-font-awesome. Preparing to unpack .../49-fonts-font-awesome_5.0.10+really4.7.0~dfsg-4.1_all.deb ... Unpacking fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../50-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../51-libjs-underscore_1.13.4~dfsg+~1.11.4-3_all.deb ... Unpacking libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../52-libjs-sphinxdoc_7.4.7-4_all.deb ... Unpacking libjs-sphinxdoc (7.4.7-4) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../53-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package libpython3.13-stdlib:arm64. Preparing to unpack .../54-libpython3.13-stdlib_3.13.0-2_arm64.deb ... Unpacking libpython3.13-stdlib:arm64 (3.13.0-2) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../55-python-babel-localedata_2.16.0-1_all.deb ... Unpacking python-babel-localedata (2.16.0-1) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../56-python3-alabaster_0.7.16-0.1_all.deb ... Unpacking python3-alabaster (0.7.16-0.1) ... Selecting previously unselected package python3.13. Preparing to unpack .../57-python3.13_3.13.0-2_arm64.deb ... Unpacking python3.13 (3.13.0-2) ... Selecting previously unselected package python3-all. Preparing to unpack .../58-python3-all_3.12.7-1_arm64.deb ... Unpacking python3-all (3.12.7-1) ... Selecting previously unselected package python3-asgiref. Preparing to unpack .../59-python3-asgiref_3.8.1-1_all.deb ... Unpacking python3-asgiref (3.8.1-1) ... Selecting previously unselected package python3-babel. Preparing to unpack .../60-python3-babel_2.16.0-1_all.deb ... Unpacking python3-babel (2.16.0-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../61-python3-certifi_2024.8.30+dfsg-1_all.deb ... Unpacking python3-certifi (2024.8.30+dfsg-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../62-python3-chardet_5.2.0+dfsg-1_all.deb ... Unpacking python3-chardet (5.2.0+dfsg-1) ... Selecting previously unselected package python3-charset-normalizer. Preparing to unpack .../63-python3-charset-normalizer_3.4.0-1+b1_arm64.deb ... Unpacking python3-charset-normalizer (3.4.0-1+b1) ... Selecting previously unselected package python3-confusable-homoglyphs. Preparing to unpack .../64-python3-confusable-homoglyphs_3.3.1-1_all.deb ... Unpacking python3-confusable-homoglyphs (3.3.1-1) ... Selecting previously unselected package python3-defusedxml. Preparing to unpack .../65-python3-defusedxml_0.7.1-2_all.deb ... Unpacking python3-defusedxml (0.7.1-2) ... Selecting previously unselected package python3-sqlparse. Preparing to unpack .../66-python3-sqlparse_0.5.2-1_all.deb ... Unpacking python3-sqlparse (0.5.2-1) ... Selecting previously unselected package python3-django. Preparing to unpack .../67-python3-django_3%3a4.2.16-1_all.deb ... Unpacking python3-django (3:4.2.16-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../68-python3-roman_4.2-1_all.deb ... Unpacking python3-roman (4.2-1) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../69-python3-docutils_0.21.2+dfsg-2_all.deb ... Unpacking python3-docutils (0.21.2+dfsg-2) ... Selecting previously unselected package python3-idna. Preparing to unpack .../70-python3-idna_3.8-2_all.deb ... Unpacking python3-idna (3.8-2) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../71-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../72-python3-markupsafe_2.1.5-1+b3_arm64.deb ... Unpacking python3-markupsafe (2.1.5-1+b3) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../73-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../74-python3-packaging_24.2-1_all.deb ... Unpacking python3-packaging (24.2-1) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../75-python3-pygments_2.18.0+dfsg-1_all.deb ... Unpacking python3-pygments (2.18.0+dfsg-1) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../76-python3-urllib3_2.0.7-2_all.deb ... Unpacking python3-urllib3 (2.0.7-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../77-python3-requests_2.32.3+dfsg-1_all.deb ... Unpacking python3-requests (2.32.3+dfsg-1) ... Selecting previously unselected package python3-snowballstemmer. Preparing to unpack .../78-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../79-sphinx-common_7.4.7-4_all.deb ... Unpacking sphinx-common (7.4.7-4) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../80-python3-sphinx_7.4.7-4_all.deb ... Unpacking python3-sphinx (7.4.7-4) ... Selecting previously unselected package sphinx-rtd-theme-common. Preparing to unpack .../81-sphinx-rtd-theme-common_3.0.2+dfsg-1_all.deb ... Unpacking sphinx-rtd-theme-common (3.0.2+dfsg-1) ... Selecting previously unselected package python3-sphinxcontrib.jquery. Preparing to unpack .../82-python3-sphinxcontrib.jquery_4.1-5_all.deb ... Unpacking python3-sphinxcontrib.jquery (4.1-5) ... Selecting previously unselected package python3-sphinx-rtd-theme. Preparing to unpack .../83-python3-sphinx-rtd-theme_3.0.2+dfsg-1_all.deb ... Unpacking python3-sphinx-rtd-theme (3.0.2+dfsg-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.8-1) ... Setting up libkeyutils1:arm64 (1.6.3-4) ... Setting up fonts-lato (2.015-1) ... Setting up libicu72:arm64 (72.1-5+b1) ... Setting up bsdextrautils (2.40.2-11) ... Setting up libmagic-mgc (1:5.45-3+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libtirpc-common (1.3.4+ds-1.3) ... Setting up libdebhelper-perl (13.20) ... Setting up libmagic1t64:arm64 (1:5.45-3+b1) ... Setting up gettext-base (0.22.5-2) ... Setting up m4 (1.4.19-4) ... Setting up libcom-err2:arm64 (1.47.1-1+b1) ... Setting up file (1:5.45-3+b1) ... Setting up libelf1t64:arm64 (0.192-4) ... Setting up python-babel-localedata (2.16.0-1) ... Setting up libkrb5support0:arm64 (1.21.3-3) ... Setting up tzdata (2024b-3) ... Current default time zone: 'Etc/UTC' Local time is now: Mon Nov 25 12:52:36 UTC 2024. Universal Time is now: Mon Nov 25 12:52:36 UTC 2024. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up libpython3.13-minimal:arm64 (3.13.0-2) ... Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.22.5-2) ... Setting up libk5crypto3:arm64 (1.21.3-3) ... Setting up autoconf (2.72-3) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libuchardet0:arm64 (0.0.8-1+b2) ... Setting up libjson-perl (4.10000-1) ... Setting up python3.13-minimal (3.13.0-2) ... Setting up netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up libkrb5-3:arm64 (1.21.3-3) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up openssl (3.3.2-2) ... Setting up readline-common (8.2-5) ... Setting up libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Setting up fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Setting up sphinx-rtd-theme-common (3.0.2+dfsg-1) ... Setting up libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... 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.14.0-1) ... Setting up gettext (0.22.5-2) ... Setting up libtool (2.4.7-8) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 146 added, 0 removed; done. Setting up libgssapi-krb5-2:arm64 (1.21.3-3) ... Setting up libjs-sphinxdoc (7.4.7-4) ... Setting up libreadline8t64:arm64 (8.2-5) ... Setting up dh-strip-nondeterminism (1.14.0-1) ... Setting up groff-base (1.23.0-5) ... Setting up xml-core (0.19) ... Setting up libpython3.13-stdlib:arm64 (3.13.0-2) ... Setting up libtirpc3t64:arm64 (1.3.4+ds-1.3+b1) ... Setting up python3.13 (3.13.0-2) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up man-db (2.13.0-1) ... Not building database; man-db/auto-update is not 'true'. Setting up sphinx-common (7.4.7-4) ... Setting up libnsl2:arm64 (1.3.0-3+b3) ... Setting up libpython3.12-stdlib:arm64 (3.12.7-3) ... Setting up python3.12 (3.12.7-3) ... Setting up debhelper (13.20) ... Setting up libpython3-stdlib:arm64 (3.12.7-1) ... Setting up python3 (3.12.7-1) ... Setting up python3-zipp (3.21.0-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up python3-markupsafe (2.1.5-1+b3) ... Setting up python3-roman (4.2-1) ... Setting up python3-jinja2 (3.1.3-1) ... Setting up python3-packaging (24.2-1) ... Setting up python3-sqlparse (0.5.2-1) ... Setting up python3-certifi (2024.8.30+dfsg-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up python3-idna (3.8-2) ... Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-urllib3 (2.0.7-2) ... Setting up python3-asgiref (3.8.1-1) ... Setting up python3-imagesize (1.4.1-1) ... Setting up python3-more-itertools (10.5.0-1) ... Setting up python3-confusable-homoglyphs (3.3.1-1) ... Setting up python3-django (3:4.2.16-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-defusedxml (0.7.1-2) ... Setting up python3-charset-normalizer (3.4.0-1+b1) ... Setting up python3-alabaster (0.7.16-0.1) ... Setting up python3-typeguard (4.4.1-1) ... Setting up python3-all (3.12.7-1) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-jaraco.text (4.0.0-1) ... Setting up python3-pkg-resources (75.2.0-1) ... Setting up python3-setuptools (75.2.0-1) ... Setting up python3-babel (2.16.0-1) ... update-alternatives: using /usr/bin/pybabel-python3 to provide /usr/bin/pybabel (pybabel) in auto mode Setting up python3-pygments (2.18.0+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-requests (2.32.3+dfsg-1) ... Setting up dh-python (6.20241024) ... Processing triggers for libc-bin (2.40-4) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.21.2+dfsg-2) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.21.2+dfsg-2) ... Setting up python3-sphinx (7.4.7-4) ... Setting up python3-sphinxcontrib.jquery (4.1-5) ... Setting up python3-sphinx-rtd-theme (3.0.2+dfsg-1) ... Processing triggers for ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. 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/python-django-registration-3.3/ && 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 > ../python-django-registration_3.3-1_source.changes dpkg-buildpackage: info: source package python-django-registration dpkg-buildpackage: info: source version 3.3-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Elena Grandi dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --with python3,sphinxdoc --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' rm -rf docs/_build/ dh_auto_clean I: pybuild base:311: python3.13 setup.py clean running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it I: pybuild base:311: python3.12 setup.py clean running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config running config I: pybuild base:311: python3.12 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' cd src/django_registration && /usr/bin/django-admin compilemessages processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fr/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nb/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/da/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/tr_TR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/de/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt_BR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/it/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/is/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_TW/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/en/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ca/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_CN/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/he/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/el/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sr/LC_MESSAGES/django.po” is already compiled and up to date. processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ar/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es_AR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/hr/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date. cd docs && /usr/bin/make html make[2]: Entering directory '/build/reproducible-path/python-django-registration-3.3/docs' sphinx-build -b html -d _build/doctrees . _build/html Running Sphinx v7.4.7 WARNING: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code. loading translations [en]... done making output directory... done Converting `source_suffix = '.rst'` to `source_suffix = {'.rst': 'restructuredtext'}`. loading intersphinx inventory 'django' from https://docs.djangoproject.com/en/stable/_objects/... loading intersphinx inventory 'python' from https://docs.python.org/3/objects.inv... WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.djangoproject.com/en/stable/_objects/' not fetchable due to : HTTPSConnectionPool(host='docs.djangoproject.com', port=443): Max retries exceeded with url: /en/stable/_objects/ (Caused by NameResolutionError(": Failed to resolve 'docs.djangoproject.com' ([Errno -3] Temporary failure in name resolution)")) WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.python.org' ([Errno -3] Temporary failure in name resolution)")) building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 16 source files that are out of date updating environment: [new config] 16 added, 0 changed, 0 removed reading sources... [ 6%] activation-workflow reading sources... [ 12%] custom-user reading sources... [ 19%] deprecations reading sources... [ 25%] exceptions reading sources... [ 31%] faq reading sources... [ 38%] forms reading sources... [ 44%] index reading sources... [ 50%] install reading sources... [ 56%] one-step-workflow reading sources... [ 62%] quickstart reading sources... [ 69%] security reading sources... [ 75%] settings reading sources... [ 81%] signals reading sources... [ 88%] upgrade reading sources... [ 94%] validators reading sources... [100%] views looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done copying assets... copying static files... done copying extra files... done copying assets: done writing output... [ 6%] activation-workflow writing output... [ 12%] custom-user writing output... [ 19%] deprecations writing output... [ 25%] exceptions writing output... [ 31%] faq writing output... [ 38%] forms writing output... [ 44%] index writing output... [ 50%] install writing output... [ 56%] one-step-workflow writing output... [ 62%] quickstart writing output... [ 69%] security writing output... [ 75%] settings writing output... [ 81%] signals writing output... [ 88%] upgrade writing output... [ 94%] validators writing output... [100%] views generating indices... genindex py-modindex done writing additional pages... search done dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 3 warnings. The HTML pages are in _build/html. Build finished. The HTML pages are in _build/html. make[2]: Leaving directory '/build/reproducible-path/python-django-registration-3.3/docs' dh_auto_build I: pybuild base:311: /usr/bin/python3.13 setup.py build running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation running egg_info creating src/django_registration.egg-info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt writing manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation running egg_info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.13 /build/reproducible-path/python-django-registration-3.3/runtests.py Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Found 73 test(s). Operations to perform: Apply all migrations: auth, contenttypes, django_registration, sessions, sites, tests Running migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_registration.0001_initial... OK Applying sessions.0001_initial... OK Applying sites.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Applying tests.0001_initial... OK System check identified no issues (0 silenced). test_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_bad_key) An invalid activation key fails to activate. ... ok test_custom_user_configured (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendViewTests.test_bad_key) An invalid activation key fails to activate. ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendViewTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_registration (tests.base.ActivationTestCase.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.base.ActivationTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.ActivationTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.ActivationTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.base.ActivationTestCase.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.base.ActivationTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.ActivationTestCase.test_registration_signal) ... ok test_case_insensitive_form (tests.test_forms.RegistrationFormTests.test_case_insensitive_form) Test the case-insensitive registration form. ... ok test_case_insensitive_validator (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator) Test the case-insensitive username validator. ... ok test_case_insensitive_validator_eq (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator_eq) Test CaseInsensitiveUnique __eq__ method. ... ok test_confusable_emails (tests.test_forms.RegistrationFormTests.test_confusable_emails) Usernames containing dangerously confusable use of Unicode are ... ok test_confusable_usernames (tests.test_forms.RegistrationFormTests.test_confusable_usernames) Usernames containing dangerously confusable use of Unicode are ... ok test_confusables_email_validator (tests.test_forms.RegistrationFormTests.test_confusables_email_validator) Test the confusable-email validator standalone. ... ok test_confusables_validator (tests.test_forms.RegistrationFormTests.test_confusables_validator) Test the confusable-username validator standalone. ... ok test_custom_reserved_names (tests.test_forms.RegistrationFormTests.test_custom_reserved_names) Reserved names can be overridden by an attribute. ... ok test_email_required (tests.test_forms.RegistrationFormTests.test_email_required) The email address field is required. ... ok test_email_uniqueness (tests.test_forms.RegistrationFormTests.test_email_uniqueness) Email uniqueness is enforced by RegistrationFormUniqueEmail. ... ok test_email_validation (tests.test_forms.RegistrationFormTests.test_email_validation) Stricter-than-RFC email validation is applied. ... ok test_email_validator (tests.test_forms.RegistrationFormTests.test_email_validator) Test the HTMl5 email address validator. ... ok test_reserved_name_non_string (tests.test_forms.RegistrationFormTests.test_reserved_name_non_string) GitHub issue #82: reserved-name validator should not attempt ... ok test_reserved_name_validator_eq (tests.test_forms.RegistrationFormTests.test_reserved_name_validator_eq) Test ReservedNameValidator __eq__ method. ... ok test_reserved_names (tests.test_forms.RegistrationFormTests.test_reserved_names) Reserved names are disallowed. ... ok test_tos_field (tests.test_forms.RegistrationFormTests.test_tos_field) The terms-of-service field on RegistrationFormTermsOfService ... ok test_username_uniqueness (tests.test_forms.RegistrationFormTests.test_username_uniqueness) Username uniqueness is enforced. ... ok test_custom_user_configured (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_signal) ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_signal) ... ok test_registration (tests.base.WorkflowTestCase.test_registration) Registration creates a new account. ... ok test_registration_closed (tests.base.WorkflowTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.WorkflowTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.WorkflowTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.base.WorkflowTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.WorkflowTestCase.test_registration_signal) ... ok test_activation (tests.test_views.ActivationViewTests.test_activation) Activation of an account functions properly when using a ... ok test_user_mismatch_breaks_view (tests.test_views.CustomUserTests.test_user_mismatch_breaks_view) When RegistrationView detects a mismatch between the model used by ... ok test_sensitive_post_parameters_are_filtered (tests.test_views.SensitiveParameterFilterTests.test_sensitive_post_parameters_are_filtered) When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- Ran 73 tests in 10.188s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... I: pybuild base:311: cd /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.12 /build/reproducible-path/python-django-registration-3.3/runtests.py Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Found 73 test(s). Operations to perform: Apply all migrations: auth, contenttypes, django_registration, sessions, sites, tests Running migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_registration.0001_initial... OK Applying sessions.0001_initial... OK Applying sites.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Applying tests.0001_initial... OK System check identified no issues (0 silenced). test_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_bad_key) An invalid activation key fails to activate. ... ok test_custom_user_configured (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendViewTests.test_bad_key) An invalid activation key fails to activate. ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendViewTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_registration (tests.base.ActivationTestCase.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.base.ActivationTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.ActivationTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.ActivationTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.base.ActivationTestCase.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.base.ActivationTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.ActivationTestCase.test_registration_signal) ... ok test_case_insensitive_form (tests.test_forms.RegistrationFormTests.test_case_insensitive_form) Test the case-insensitive registration form. ... ok test_case_insensitive_validator (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator) Test the case-insensitive username validator. ... ok test_case_insensitive_validator_eq (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator_eq) Test CaseInsensitiveUnique __eq__ method. ... ok test_confusable_emails (tests.test_forms.RegistrationFormTests.test_confusable_emails) Usernames containing dangerously confusable use of Unicode are ... ok test_confusable_usernames (tests.test_forms.RegistrationFormTests.test_confusable_usernames) Usernames containing dangerously confusable use of Unicode are ... ok test_confusables_email_validator (tests.test_forms.RegistrationFormTests.test_confusables_email_validator) Test the confusable-email validator standalone. ... ok test_confusables_validator (tests.test_forms.RegistrationFormTests.test_confusables_validator) Test the confusable-username validator standalone. ... ok test_custom_reserved_names (tests.test_forms.RegistrationFormTests.test_custom_reserved_names) Reserved names can be overridden by an attribute. ... ok test_email_required (tests.test_forms.RegistrationFormTests.test_email_required) The email address field is required. ... ok test_email_uniqueness (tests.test_forms.RegistrationFormTests.test_email_uniqueness) Email uniqueness is enforced by RegistrationFormUniqueEmail. ... ok test_email_validation (tests.test_forms.RegistrationFormTests.test_email_validation) Stricter-than-RFC email validation is applied. ... ok test_email_validator (tests.test_forms.RegistrationFormTests.test_email_validator) Test the HTMl5 email address validator. ... ok test_reserved_name_non_string (tests.test_forms.RegistrationFormTests.test_reserved_name_non_string) GitHub issue #82: reserved-name validator should not attempt ... ok test_reserved_name_validator_eq (tests.test_forms.RegistrationFormTests.test_reserved_name_validator_eq) Test ReservedNameValidator __eq__ method. ... ok test_reserved_names (tests.test_forms.RegistrationFormTests.test_reserved_names) Reserved names are disallowed. ... ok test_tos_field (tests.test_forms.RegistrationFormTests.test_tos_field) The terms-of-service field on RegistrationFormTermsOfService ... ok test_username_uniqueness (tests.test_forms.RegistrationFormTests.test_username_uniqueness) Username uniqueness is enforced. ... ok test_custom_user_configured (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_signal) ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_signal) ... ok test_registration (tests.base.WorkflowTestCase.test_registration) Registration creates a new account. ... ok test_registration_closed (tests.base.WorkflowTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.WorkflowTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.WorkflowTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.base.WorkflowTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.WorkflowTestCase.test_registration_signal) ... ok test_activation (tests.test_views.ActivationViewTests.test_activation) Activation of an account functions properly when using a ... ok test_user_mismatch_breaks_view (tests.test_views.CustomUserTests.test_user_mismatch_breaks_view) When RegistrationView detects a mismatch between the model used by ... ok test_sensitive_post_parameters_are_filtered (tests.test_views.SensitiveParameterFilterTests.test_sensitive_post_parameters_are_filtered) When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- Ran 73 tests in 10.306s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild debian/rules override_dh_auto_install make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' # dh_auto_install expects the following directory to exist (before it # is created?) mkdir -p debian/python-django-registration-doc dh_auto_install I: pybuild base:311: /usr/bin/python3.13 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration 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 src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.__pycache__' to be distributed and are already explicitly excluding 'django_registration.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.activation.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.activation.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.activation.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.activation.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.activation.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.one_step.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.one_step.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.one_step.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.one_step.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.one_step.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.migrations.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.migrations.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.migrations.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.migrations.__pycache__' to be distributed and are already explicitly excluding 'django_registration.migrations.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/views.py to views.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/views.py to views.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/exceptions.py to exceptions.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/forms.py to forms.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/signals.py to signals.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/validators.py to validators.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/views.py to views.cpython-313.pyc running install_egg_info Copying src/django_registration.egg-info to /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration-3.3.egg-info Skipping SOURCES.txt running install_scripts I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration 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 src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.__pycache__' to be distributed and are already explicitly excluding 'django_registration.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.activation.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.activation.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.activation.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.activation.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.activation.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.one_step.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.one_step.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.one_step.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.one_step.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.one_step.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.migrations.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.migrations.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.migrations.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.migrations.__pycache__' to be distributed and are already explicitly excluding 'django_registration.migrations.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/exceptions.py to exceptions.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/forms.py to forms.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/signals.py to signals.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/validators.py to validators.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/views.py to views.cpython-312.pyc running install_egg_info Copying src/django_registration.egg-info to /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration-3.3.egg-info Skipping SOURCES.txt running install_scripts # Drop .po files and keep only .mo files (compiled) find debian/python3-django-registration/ -name '*.po' -exec rm -v {} \; ; find debian/python-django-registration-doc/ -name '*.po' -exec rm -v {} \; ; removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_installdocs -O--buildsystem=pybuild dh_installdocs: warning: Cannot auto-detect main package for python-django-registration-doc. If the default is wrong, please use --doc-main-package dh_sphinxdoc -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 Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/it/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/is/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/he/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/en/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/el/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/de/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/da/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.mo 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 dpkg-gencontrol: warning: package python-django-registration-doc: substitution variable ${sphinxdoc:Built-Using} unused, but is defined dpkg-gencontrol: warning: Depends field of package python3-django-registration: substitution variable ${sphinxdoc:Depends} used, but is not defined dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-django-registration' in '../python3-django-registration_3.3-1_all.deb'. dpkg-deb: building package 'python-django-registration-doc' in '../python-django-registration-doc_3.3-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python-django-registration_3.3-1_arm64.buildinfo dpkg-genchanges --build=binary -O../python-django-registration_3.3-1_arm64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /srv/workspace/pbuilder/3825326 and its subdirectories I: Current time: Mon Nov 25 00:53:46 -12 2024 I: pbuilder-time-stamp: 1732539226 Mon Nov 25 12:53:48 UTC 2024 I: 1st build successful. Starting 2nd build on remote node codethink01-arm64.debian.net. Mon Nov 25 12:53:48 UTC 2024 I: Preparing to do remote build '2' on codethink01-arm64.debian.net. Mon Nov 25 12:53:48 UTC 2024 - checking /var/lib/jenkins/offline_nodes if codethink01-arm64.debian.net is marked as down. Mon Nov 25 12:53:48 UTC 2024 - checking via ssh if codethink01-arm64.debian.net is up. removed '/tmp/read-only-fs-test-QLGIPy' ==================================================================================== Sun Dec 28 19:16:49 UTC 2025 - running /srv/jenkins/bin/reproducible_build.sh (for job /srv/jenkins/bin/reproducible_build.sh) on codethink01-arm64, called using "2 python-django-registration unstable /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy 3.3-1" as arguments. Sun Dec 28 19:16:49 UTC 2025 - actually running "reproducible_build.sh" (md5sum 68e686e434c9ab7bc3ec047d8b309cbc) as "/tmp/jenkins-script-r5zJBFI2" $ git clone https://salsa.debian.org/qa/jenkins.debian.net.git ; more CONTRIBUTING Sun Dec 28 19:16:49 UTC 2025 I: Downloading source for unstable/python-django-registration=3.3-1 Reading package lists... NOTICE: 'python-django-registration' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/python-team/packages/python-django-registration.git Please use: git clone https://salsa.debian.org/python-team/packages/python-django-registration.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 98.6 kB of source archives. Get:1 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (dsc) [2355 B] Get:2 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (tar) [85.0 kB] Get:3 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (asc) [833 B] Get:4 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (diff) [10.4 kB] Fetched 98.6 kB in 0s (7267 kB/s) Download complete and in download only mode Reading package lists... NOTICE: 'python-django-registration' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/python-team/packages/python-django-registration.git Please use: git clone https://salsa.debian.org/python-team/packages/python-django-registration.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 98.6 kB of source archives. Get:1 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (dsc) [2355 B] Get:2 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (tar) [85.0 kB] Get:3 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (asc) [833 B] Get:4 http://deb.debian.org/debian unstable/main python-django-registration 3.3-1 (diff) [10.4 kB] Fetched 98.6 kB in 0s (7267 kB/s) Download complete and in download only mode ============================================================================= Re-Building python-django-registration in unstable on arm64 on codethink01-arm64 now. Date: Sun Dec 28 19:16:50 GMT 2025 Date UTC: Sun Dec 28 19:16:50 UTC 2025 ============================================================================= ++ mktemp -t pbuilderrc_XXXX --tmpdir=/srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy + local TMPCFG=/srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/pbuilderrc_djor + case ${ARCH} in + case $ARCH in + locale=nl_BE + language=nl + case "${SUITE}" in + reproducible_buildflags=+all + extra_deb_build_options= + case "${SRCPACKAGE}" in + cat + echo BUILDDIR=/build/reproducible-path + '[' python-django-registration = debian-installer -o python-django-registration = debian-installer-netboot-images ']' + pbuilder_options=() + local pbuilder_options + DEBBUILDOPTS=-b + BINARYTARGET= + '[' python-django-registration = u-boot ']' + case "${SRCPACKAGE}" in + PBUILDERTIMEOUT=24 + local PRESULT=0 + sudo timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/pbuilderrc_djor --distribution unstable --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2 --logfile b2/build.log python-django-registration_3.3-1.dsc W: /root/.pbuilderrc does not exist I: Logging to b2/build.log I: pbuilder: network access will be disabled during build I: Current time: Mon Dec 29 09:16:50 +14 2025 I: pbuilder-time-stamp: 1766949410 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Copying source file I: copying [python-django-registration_3.3-1.dsc] I: copying [./python-django-registration_3.3.orig.tar.gz] I: copying [./python-django-registration_3.3.orig.tar.gz.asc] I: copying [./python-django-registration_3.3-1.debian.tar.xz] I: Extracting source gpgv: Signature made Mon Oct 24 11:37:05 2022 gpgv: using RSA key 63C9FAAC68393E94CF925E1970BD22D31123B431 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./python-django-registration_3.3-1.dsc: no acceptable signature found dpkg-source: info: extracting python-django-registration in python-django-registration-3.3 dpkg-source: info: unpacking python-django-registration_3.3.orig.tar.gz dpkg-source: info: unpacking python-django-registration_3.3-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D01_modify_environment starting debug: Running on codethink01-arm64. I: Changing host+domainname to test build reproducibility I: Adding a custom variable just for the fun of it... I: Changing /bin/sh to bash '/bin/sh' -> '/bin/bash' lrwxrwxrwx 1 root root 9 Dec 28 19:16 /bin/sh -> /bin/bash I: Setting pbuilder2's login shell to /bin/bash I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D01_modify_environment finished I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D02_print_environment starting I: set BASH=/bin/sh BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:globskipdots:hostcomplete:interactive_comments:patsub_replacement:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_LINENO=([0]="12" [1]="0") BASH_LOADABLES_PATH=/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib/bash:. BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") BASH_VERSINFO=([0]="5" [1]="2" [2]="32" [3]="1" [4]="release" [5]="aarch64-unknown-linux-gnu") BASH_VERSION='5.2.32(1)-release' BUILDDIR=/build/reproducible-path BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' BUILDUSERNAME=pbuilder2 BUILD_ARCH=arm64 DEBIAN_FRONTEND=noninteractive DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' DIRSTACK=() DISTRIBUTION=unstable EUID=0 FUNCNAME=([0]="Echo" [1]="main") GROUPS=() HOME=/root HOSTNAME=i-capture-the-hostname HOSTTYPE=aarch64 HOST_ARCH=arm64 IFS=' ' INVOCATION_ID=4dc1c65e81b64066bd9fd00344cfc6c5 LANG=C LANGUAGE=nl_BE:nl LC_ALL=C MACHTYPE=aarch64-unknown-linux-gnu MAIL=/var/mail/root OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path PBCURRENTCOMMANDLINEOPERATION=build PBUILDER_OPERATION=build PBUILDER_PKGDATADIR=/usr/share/pbuilder PBUILDER_PKGLIBDIR=/usr/lib/pbuilder PBUILDER_SYSCONFDIR=/etc PIPESTATUS=([0]="0") POSIXLY_CORRECT=y PPID=344925 PS4='+ ' PWD=/ SHELL=/bin/bash SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix SHLVL=3 SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/pbuilderrc_djor --distribution unstable --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2 --logfile b2/build.log python-django-registration_3.3-1.dsc' SUDO_GID=109 SUDO_UID=104 SUDO_USER=jenkins TERM=unknown TZ=/usr/share/zoneinfo/Etc/GMT-14 UID=0 USER=root _='I: set' http_proxy=http://192.168.101.4:3128 I: uname -a Linux i-capture-the-hostname 6.1.0-28-cloud-arm64 #1 SMP Debian 6.1.119-1 (2024-11-22) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 Nov 22 2024 /bin -> usr/bin I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: arm64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper-compat (= 13), dh-python, python3-all, python3-setuptools, python3-confusable-homoglyphs (>= 3), python3-django, python3-sphinx, python3-sphinx-rtd-theme dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20083 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-all; however: Package python3-all is not installed. pbuilder-satisfydepends-dummy depends on python3-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3-confusable-homoglyphs (>= 3); however: Package python3-confusable-homoglyphs is not installed. pbuilder-satisfydepends-dummy depends on python3-django; however: Package python3-django is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx; however: Package python3-sphinx is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx-rtd-theme; however: Package python3-sphinx-rtd-theme 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} ca-certificates{a} debhelper{a} dh-autoreconf{a} dh-python{a} dh-strip-nondeterminism{a} docutils-common{a} dwz{a} file{a} fonts-font-awesome{a} fonts-lato{a} gettext{a} gettext-base{a} groff-base{a} intltool-debian{a} libarchive-zip-perl{a} libcom-err2{a} libdebhelper-perl{a} libelf1t64{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libgssapi-krb5-2{a} libicu72{a} libjs-jquery{a} libjs-sphinxdoc{a} libjs-underscore{a} libjson-perl{a} libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} libmagic-mgc{a} libmagic1t64{a} libnsl2{a} libpipeline1{a} libpython3-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libpython3.13-minimal{a} libpython3.13-stdlib{a} libreadline8t64{a} libtirpc-common{a} libtirpc3t64{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} po-debconf{a} python-babel-localedata{a} python3{a} python3-alabaster{a} python3-all{a} python3-asgiref{a} python3-autocommand{a} python3-babel{a} python3-certifi{a} python3-chardet{a} python3-charset-normalizer{a} python3-confusable-homoglyphs{a} python3-defusedxml{a} python3-django{a} python3-docutils{a} python3-idna{a} python3-imagesize{a} python3-inflect{a} python3-jaraco.context{a} python3-jaraco.functools{a} python3-jaraco.text{a} python3-jinja2{a} python3-markupsafe{a} python3-minimal{a} python3-more-itertools{a} python3-packaging{a} python3-pkg-resources{a} python3-pygments{a} python3-requests{a} python3-roman{a} python3-setuptools{a} python3-snowballstemmer{a} python3-sphinx{a} python3-sphinx-rtd-theme{a} python3-sphinxcontrib.jquery{a} python3-sqlparse{a} python3-typeguard{a} python3-typing-extensions{a} python3-urllib3{a} python3-zipp{a} python3.12{a} python3.12-minimal{a} python3.13{a} python3.13-minimal{a} readline-common{a} sensible-utils{a} sgml-base{a} sphinx-common{a} sphinx-rtd-theme-common{a} tzdata{a} xml-core{a} The following packages are RECOMMENDED but will NOT be installed: curl javascript-common krb5-locales libarchive-cpio-perl libjson-xs-perl libltdl-dev libmail-sendmail-perl libpaper-utils lynx python3-click python3-pil python3-tz wget 0 packages upgraded, 106 newly installed, 0 to remove and 0 not upgraded. Need to get 51.6 MB of archives. After unpacking 234 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian unstable/main arm64 fonts-lato all 2.015-1 [2780 kB] Get: 2 http://deb.debian.org/debian unstable/main arm64 libpython3.12-minimal arm64 3.12.7-3 [808 kB] Get: 3 http://deb.debian.org/debian unstable/main arm64 libexpat1 arm64 2.6.4-1 [90.7 kB] Get: 4 http://deb.debian.org/debian unstable/main arm64 python3.12-minimal arm64 3.12.7-3 [1940 kB] Get: 5 http://deb.debian.org/debian unstable/main arm64 python3-minimal arm64 3.12.7-1 [26.8 kB] Get: 6 http://deb.debian.org/debian unstable/main arm64 media-types all 10.1.0 [26.9 kB] Get: 7 http://deb.debian.org/debian unstable/main arm64 netbase all 6.4 [12.8 kB] Get: 8 http://deb.debian.org/debian unstable/main arm64 tzdata all 2024b-3 [255 kB] Get: 9 http://deb.debian.org/debian unstable/main arm64 libkrb5support0 arm64 1.21.3-3 [32.1 kB] Get: 10 http://deb.debian.org/debian unstable/main arm64 libcom-err2 arm64 1.47.1-1+b1 [23.1 kB] Get: 11 http://deb.debian.org/debian unstable/main arm64 libk5crypto3 arm64 1.21.3-3 [80.8 kB] Get: 12 http://deb.debian.org/debian unstable/main arm64 libkeyutils1 arm64 1.6.3-4 [9352 B] Get: 13 http://deb.debian.org/debian unstable/main arm64 libkrb5-3 arm64 1.21.3-3 [310 kB] Get: 14 http://deb.debian.org/debian unstable/main arm64 libgssapi-krb5-2 arm64 1.21.3-3 [126 kB] Get: 15 http://deb.debian.org/debian unstable/main arm64 libtirpc-common all 1.3.4+ds-1.3 [10.9 kB] Get: 16 http://deb.debian.org/debian unstable/main arm64 libtirpc3t64 arm64 1.3.4+ds-1.3+b1 [78.7 kB] Get: 17 http://deb.debian.org/debian unstable/main arm64 libnsl2 arm64 1.3.0-3+b3 [37.9 kB] Get: 18 http://deb.debian.org/debian unstable/main arm64 readline-common all 8.2-5 [69.3 kB] Get: 19 http://deb.debian.org/debian unstable/main arm64 libreadline8t64 arm64 8.2-5 [159 kB] Get: 20 http://deb.debian.org/debian unstable/main arm64 libpython3.12-stdlib arm64 3.12.7-3 [1902 kB] Get: 21 http://deb.debian.org/debian unstable/main arm64 python3.12 arm64 3.12.7-3 [671 kB] Get: 22 http://deb.debian.org/debian unstable/main arm64 libpython3-stdlib arm64 3.12.7-1 [9708 B] Get: 23 http://deb.debian.org/debian unstable/main arm64 python3 arm64 3.12.7-1 [27.8 kB] Get: 24 http://deb.debian.org/debian unstable/main arm64 libpython3.13-minimal arm64 3.13.0-2 [850 kB] Get: 25 http://deb.debian.org/debian unstable/main arm64 python3.13-minimal arm64 3.13.0-2 [1838 kB] Get: 26 http://deb.debian.org/debian unstable/main arm64 sgml-base all 1.31 [15.4 kB] Get: 27 http://deb.debian.org/debian unstable/main arm64 sensible-utils all 0.0.24 [24.8 kB] Get: 28 http://deb.debian.org/debian unstable/main arm64 openssl arm64 3.3.2-2 [1347 kB] Get: 29 http://deb.debian.org/debian unstable/main arm64 ca-certificates all 20240203 [158 kB] Get: 30 http://deb.debian.org/debian unstable/main arm64 libmagic-mgc arm64 1:5.45-3+b1 [314 kB] Get: 31 http://deb.debian.org/debian unstable/main arm64 libmagic1t64 arm64 1:5.45-3+b1 [102 kB] Get: 32 http://deb.debian.org/debian unstable/main arm64 file arm64 1:5.45-3+b1 [43.4 kB] Get: 33 http://deb.debian.org/debian unstable/main arm64 gettext-base arm64 0.22.5-2 [198 kB] Get: 34 http://deb.debian.org/debian unstable/main arm64 libuchardet0 arm64 0.0.8-1+b2 [69.2 kB] Get: 35 http://deb.debian.org/debian unstable/main arm64 groff-base arm64 1.23.0-5 [1129 kB] Get: 36 http://deb.debian.org/debian unstable/main arm64 bsdextrautils arm64 2.40.2-11 [91.2 kB] Get: 37 http://deb.debian.org/debian unstable/main arm64 libpipeline1 arm64 1.5.8-1 [40.2 kB] Get: 38 http://deb.debian.org/debian unstable/main arm64 man-db arm64 2.13.0-1 [1404 kB] Get: 39 http://deb.debian.org/debian unstable/main arm64 m4 arm64 1.4.19-4 [277 kB] Get: 40 http://deb.debian.org/debian unstable/main arm64 autoconf all 2.72-3 [493 kB] Get: 41 http://deb.debian.org/debian unstable/main arm64 autotools-dev all 20220109.1 [51.6 kB] Get: 42 http://deb.debian.org/debian unstable/main arm64 automake all 1:1.16.5-1.3 [823 kB] Get: 43 http://deb.debian.org/debian unstable/main arm64 autopoint all 0.22.5-2 [723 kB] Get: 44 http://deb.debian.org/debian unstable/main arm64 libdebhelper-perl all 13.20 [89.7 kB] Get: 45 http://deb.debian.org/debian unstable/main arm64 libtool all 2.4.7-8 [517 kB] Get: 46 http://deb.debian.org/debian unstable/main arm64 dh-autoreconf all 20 [17.1 kB] Get: 47 http://deb.debian.org/debian unstable/main arm64 libarchive-zip-perl all 1.68-1 [104 kB] Get: 48 http://deb.debian.org/debian unstable/main arm64 libfile-stripnondeterminism-perl all 1.14.0-1 [19.5 kB] Get: 49 http://deb.debian.org/debian unstable/main arm64 dh-strip-nondeterminism all 1.14.0-1 [8448 B] Get: 50 http://deb.debian.org/debian unstable/main arm64 libelf1t64 arm64 0.192-4 [189 kB] Get: 51 http://deb.debian.org/debian unstable/main arm64 dwz arm64 0.15-1+b1 [102 kB] Get: 52 http://deb.debian.org/debian unstable/main arm64 libicu72 arm64 72.1-5+b1 [9239 kB] Get: 53 http://deb.debian.org/debian unstable/main arm64 libxml2 arm64 2.12.7+dfsg+really2.9.14-0.2+b1 [630 kB] Get: 54 http://deb.debian.org/debian unstable/main arm64 gettext arm64 0.22.5-2 [1532 kB] Get: 55 http://deb.debian.org/debian unstable/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 56 http://deb.debian.org/debian unstable/main arm64 po-debconf all 1.0.21+nmu1 [248 kB] Get: 57 http://deb.debian.org/debian unstable/main arm64 debhelper all 13.20 [915 kB] Get: 58 http://deb.debian.org/debian unstable/main arm64 python3-autocommand all 2.2.2-3 [13.6 kB] Get: 59 http://deb.debian.org/debian unstable/main arm64 python3-more-itertools all 10.5.0-1 [63.8 kB] Get: 60 http://deb.debian.org/debian unstable/main arm64 python3-typing-extensions all 4.12.2-2 [73.0 kB] Get: 61 http://deb.debian.org/debian unstable/main arm64 python3-typeguard all 4.4.1-1 [37.0 kB] Get: 62 http://deb.debian.org/debian unstable/main arm64 python3-inflect all 7.3.1-2 [32.4 kB] Get: 63 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.context all 6.0.0-1 [7984 B] Get: 64 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.functools all 4.1.0-1 [12.0 kB] Get: 65 http://deb.debian.org/debian unstable/main arm64 python3-pkg-resources all 75.2.0-1 [213 kB] Get: 66 http://deb.debian.org/debian unstable/main arm64 python3-jaraco.text all 4.0.0-1 [11.4 kB] Get: 67 http://deb.debian.org/debian unstable/main arm64 python3-zipp all 3.21.0-1 [10.6 kB] Get: 68 http://deb.debian.org/debian unstable/main arm64 python3-setuptools all 75.2.0-1 [731 kB] Get: 69 http://deb.debian.org/debian unstable/main arm64 dh-python all 6.20241024 [109 kB] Get: 70 http://deb.debian.org/debian unstable/main arm64 xml-core all 0.19 [20.1 kB] Get: 71 http://deb.debian.org/debian unstable/main arm64 docutils-common all 0.21.2+dfsg-2 [128 kB] Get: 72 http://deb.debian.org/debian unstable/main arm64 fonts-font-awesome all 5.0.10+really4.7.0~dfsg-4.1 [517 kB] Get: 73 http://deb.debian.org/debian unstable/main arm64 libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get: 74 http://deb.debian.org/debian unstable/main arm64 libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get: 75 http://deb.debian.org/debian unstable/main arm64 libjs-sphinxdoc all 7.4.7-4 [158 kB] Get: 76 http://deb.debian.org/debian unstable/main arm64 libjson-perl all 4.10000-1 [87.5 kB] Get: 77 http://deb.debian.org/debian unstable/main arm64 libpython3.13-stdlib arm64 3.13.0-2 [1922 kB] Get: 78 http://deb.debian.org/debian unstable/main arm64 python-babel-localedata all 2.16.0-1 [5696 kB] Get: 79 http://deb.debian.org/debian unstable/main arm64 python3-alabaster all 0.7.16-0.1 [27.9 kB] Get: 80 http://deb.debian.org/debian unstable/main arm64 python3.13 arm64 3.13.0-2 [730 kB] Get: 81 http://deb.debian.org/debian unstable/main arm64 python3-all arm64 3.12.7-1 [1052 B] Get: 82 http://deb.debian.org/debian unstable/main arm64 python3-asgiref all 3.8.1-1 [28.8 kB] Get: 83 http://deb.debian.org/debian unstable/main arm64 python3-babel all 2.16.0-1 [114 kB] Get: 84 http://deb.debian.org/debian unstable/main arm64 python3-certifi all 2024.8.30+dfsg-1 [9576 B] Get: 85 http://deb.debian.org/debian unstable/main arm64 python3-chardet all 5.2.0+dfsg-1 [107 kB] Get: 86 http://deb.debian.org/debian unstable/main arm64 python3-charset-normalizer arm64 3.4.0-1+b1 [129 kB] Get: 87 http://deb.debian.org/debian unstable/main arm64 python3-confusable-homoglyphs all 3.3.1-1 [128 kB] Get: 88 http://deb.debian.org/debian unstable/main arm64 python3-defusedxml all 0.7.1-2 [43.3 kB] Get: 89 http://deb.debian.org/debian unstable/main arm64 python3-sqlparse all 0.5.2-1 [39.7 kB] Get: 90 http://deb.debian.org/debian unstable/main arm64 python3-django all 3:4.2.16-1 [2738 kB] Get: 91 http://deb.debian.org/debian unstable/main arm64 python3-roman all 4.2-1 [10.4 kB] Get: 92 http://deb.debian.org/debian unstable/main arm64 python3-docutils all 0.21.2+dfsg-2 [403 kB] Get: 93 http://deb.debian.org/debian unstable/main arm64 python3-idna all 3.8-2 [41.6 kB] Get: 94 http://deb.debian.org/debian unstable/main arm64 python3-imagesize all 1.4.1-1 [6688 B] Get: 95 http://deb.debian.org/debian unstable/main arm64 python3-markupsafe arm64 2.1.5-1+b3 [14.0 kB] Get: 96 http://deb.debian.org/debian unstable/main arm64 python3-jinja2 all 3.1.3-1 [119 kB] Get: 97 http://deb.debian.org/debian unstable/main arm64 python3-packaging all 24.2-1 [55.3 kB] Get: 98 http://deb.debian.org/debian unstable/main arm64 python3-pygments all 2.18.0+dfsg-1 [836 kB] Get: 99 http://deb.debian.org/debian unstable/main arm64 python3-urllib3 all 2.0.7-2 [111 kB] Get: 100 http://deb.debian.org/debian unstable/main arm64 python3-requests all 2.32.3+dfsg-1 [71.9 kB] Get: 101 http://deb.debian.org/debian unstable/main arm64 python3-snowballstemmer all 2.2.0-4 [58.0 kB] Get: 102 http://deb.debian.org/debian unstable/main arm64 sphinx-common all 7.4.7-4 [731 kB] Get: 103 http://deb.debian.org/debian unstable/main arm64 python3-sphinx all 7.4.7-4 [588 kB] Get: 104 http://deb.debian.org/debian unstable/main arm64 sphinx-rtd-theme-common all 3.0.2+dfsg-1 [1023 kB] Get: 105 http://deb.debian.org/debian unstable/main arm64 python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 106 http://deb.debian.org/debian unstable/main arm64 python3-sphinx-rtd-theme all 3.0.2+dfsg-1 [29.5 kB] Fetched 51.6 MB in 0s (175 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package fonts-lato. (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 ... 20083 files and directories currently installed.) Preparing to unpack .../fonts-lato_2.015-1_all.deb ... Unpacking fonts-lato (2.015-1) ... Selecting previously unselected package libpython3.12-minimal:arm64. Preparing to unpack .../libpython3.12-minimal_3.12.7-3_arm64.deb ... Unpacking libpython3.12-minimal:arm64 (3.12.7-3) ... Selecting previously unselected package libexpat1:arm64. Preparing to unpack .../libexpat1_2.6.4-1_arm64.deb ... Unpacking libexpat1:arm64 (2.6.4-1) ... Selecting previously unselected package python3.12-minimal. Preparing to unpack .../python3.12-minimal_3.12.7-3_arm64.deb ... Unpacking python3.12-minimal (3.12.7-3) ... Setting up libpython3.12-minimal:arm64 (3.12.7-3) ... Setting up libexpat1:arm64 (2.6.4-1) ... Setting up python3.12-minimal (3.12.7-3) ... 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 ... 20429 files and directories currently installed.) Preparing to unpack .../00-python3-minimal_3.12.7-1_arm64.deb ... Unpacking python3-minimal (3.12.7-1) ... Selecting previously unselected package media-types. Preparing to unpack .../01-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../02-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package tzdata. Preparing to unpack .../03-tzdata_2024b-3_all.deb ... Unpacking tzdata (2024b-3) ... Selecting previously unselected package libkrb5support0:arm64. Preparing to unpack .../04-libkrb5support0_1.21.3-3_arm64.deb ... Unpacking libkrb5support0:arm64 (1.21.3-3) ... Selecting previously unselected package libcom-err2:arm64. Preparing to unpack .../05-libcom-err2_1.47.1-1+b1_arm64.deb ... Unpacking libcom-err2:arm64 (1.47.1-1+b1) ... Selecting previously unselected package libk5crypto3:arm64. Preparing to unpack .../06-libk5crypto3_1.21.3-3_arm64.deb ... Unpacking libk5crypto3:arm64 (1.21.3-3) ... Selecting previously unselected package libkeyutils1:arm64. Preparing to unpack .../07-libkeyutils1_1.6.3-4_arm64.deb ... Unpacking libkeyutils1:arm64 (1.6.3-4) ... Selecting previously unselected package libkrb5-3:arm64. Preparing to unpack .../08-libkrb5-3_1.21.3-3_arm64.deb ... Unpacking libkrb5-3:arm64 (1.21.3-3) ... Selecting previously unselected package libgssapi-krb5-2:arm64. Preparing to unpack .../09-libgssapi-krb5-2_1.21.3-3_arm64.deb ... Unpacking libgssapi-krb5-2:arm64 (1.21.3-3) ... Selecting previously unselected package libtirpc-common. Preparing to unpack .../10-libtirpc-common_1.3.4+ds-1.3_all.deb ... Unpacking libtirpc-common (1.3.4+ds-1.3) ... Selecting previously unselected package libtirpc3t64:arm64. Preparing to unpack .../11-libtirpc3t64_1.3.4+ds-1.3+b1_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libtirpc.so.3 to /lib/aarch64-linux-gnu/libtirpc.so.3.usr-is-merged by libtirpc3t64' Adding 'diversion of /lib/aarch64-linux-gnu/libtirpc.so.3.0.0 to /lib/aarch64-linux-gnu/libtirpc.so.3.0.0.usr-is-merged by libtirpc3t64' Unpacking libtirpc3t64:arm64 (1.3.4+ds-1.3+b1) ... Selecting previously unselected package libnsl2:arm64. Preparing to unpack .../12-libnsl2_1.3.0-3+b3_arm64.deb ... Unpacking libnsl2:arm64 (1.3.0-3+b3) ... Selecting previously unselected package readline-common. Preparing to unpack .../13-readline-common_8.2-5_all.deb ... Unpacking readline-common (8.2-5) ... Selecting previously unselected package libreadline8t64:arm64. Preparing to unpack .../14-libreadline8t64_8.2-5_arm64.deb ... Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8 to /lib/aarch64-linux-gnu/libhistory.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libhistory.so.8.2 to /lib/aarch64-linux-gnu/libhistory.so.8.2.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8 to /lib/aarch64-linux-gnu/libreadline.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/aarch64-linux-gnu/libreadline.so.8.2 to /lib/aarch64-linux-gnu/libreadline.so.8.2.usr-is-merged by libreadline8t64' Unpacking libreadline8t64:arm64 (8.2-5) ... Selecting previously unselected package libpython3.12-stdlib:arm64. Preparing to unpack .../15-libpython3.12-stdlib_3.12.7-3_arm64.deb ... Unpacking libpython3.12-stdlib:arm64 (3.12.7-3) ... Selecting previously unselected package python3.12. Preparing to unpack .../16-python3.12_3.12.7-3_arm64.deb ... Unpacking python3.12 (3.12.7-3) ... Selecting previously unselected package libpython3-stdlib:arm64. Preparing to unpack .../17-libpython3-stdlib_3.12.7-1_arm64.deb ... Unpacking libpython3-stdlib:arm64 (3.12.7-1) ... Setting up python3-minimal (3.12.7-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 ... 21491 files and directories currently installed.) Preparing to unpack .../00-python3_3.12.7-1_arm64.deb ... Unpacking python3 (3.12.7-1) ... Selecting previously unselected package libpython3.13-minimal:arm64. Preparing to unpack .../01-libpython3.13-minimal_3.13.0-2_arm64.deb ... Unpacking libpython3.13-minimal:arm64 (3.13.0-2) ... Selecting previously unselected package python3.13-minimal. Preparing to unpack .../02-python3.13-minimal_3.13.0-2_arm64.deb ... Unpacking python3.13-minimal (3.13.0-2) ... Selecting previously unselected package sgml-base. Preparing to unpack .../03-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../04-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package openssl. Preparing to unpack .../05-openssl_3.3.2-2_arm64.deb ... Unpacking openssl (3.3.2-2) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../06-ca-certificates_20240203_all.deb ... Unpacking ca-certificates (20240203) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../07-libmagic-mgc_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic-mgc (1:5.45-3+b1) ... Selecting previously unselected package libmagic1t64:arm64. Preparing to unpack .../08-libmagic1t64_1%3a5.45-3+b1_arm64.deb ... Unpacking libmagic1t64:arm64 (1:5.45-3+b1) ... Selecting previously unselected package file. Preparing to unpack .../09-file_1%3a5.45-3+b1_arm64.deb ... Unpacking file (1:5.45-3+b1) ... Selecting previously unselected package gettext-base. Preparing to unpack .../10-gettext-base_0.22.5-2_arm64.deb ... Unpacking gettext-base (0.22.5-2) ... Selecting previously unselected package libuchardet0:arm64. Preparing to unpack .../11-libuchardet0_0.0.8-1+b2_arm64.deb ... Unpacking libuchardet0:arm64 (0.0.8-1+b2) ... Selecting previously unselected package groff-base. Preparing to unpack .../12-groff-base_1.23.0-5_arm64.deb ... Unpacking groff-base (1.23.0-5) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../13-bsdextrautils_2.40.2-11_arm64.deb ... Unpacking bsdextrautils (2.40.2-11) ... Selecting previously unselected package libpipeline1:arm64. Preparing to unpack .../14-libpipeline1_1.5.8-1_arm64.deb ... Unpacking libpipeline1:arm64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../15-man-db_2.13.0-1_arm64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../16-m4_1.4.19-4_arm64.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../17-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../18-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../19-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 .../20-autopoint_0.22.5-2_all.deb ... Unpacking autopoint (0.22.5-2) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../21-libdebhelper-perl_13.20_all.deb ... Unpacking libdebhelper-perl (13.20) ... Selecting previously unselected package libtool. Preparing to unpack .../22-libtool_2.4.7-8_all.deb ... Unpacking libtool (2.4.7-8) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../23-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../24-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../25-libfile-stripnondeterminism-perl_1.14.0-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.0-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../26-dh-strip-nondeterminism_1.14.0-1_all.deb ... Unpacking dh-strip-nondeterminism (1.14.0-1) ... Selecting previously unselected package libelf1t64:arm64. Preparing to unpack .../27-libelf1t64_0.192-4_arm64.deb ... Unpacking libelf1t64:arm64 (0.192-4) ... Selecting previously unselected package dwz. Preparing to unpack .../28-dwz_0.15-1+b1_arm64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libicu72:arm64. Preparing to unpack .../29-libicu72_72.1-5+b1_arm64.deb ... Unpacking libicu72:arm64 (72.1-5+b1) ... Selecting previously unselected package libxml2:arm64. Preparing to unpack .../30-libxml2_2.12.7+dfsg+really2.9.14-0.2+b1_arm64.deb ... Unpacking libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Selecting previously unselected package gettext. Preparing to unpack .../31-gettext_0.22.5-2_arm64.deb ... Unpacking gettext (0.22.5-2) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../32-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 .../33-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../34-debhelper_13.20_all.deb ... Unpacking debhelper (13.20) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../35-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../36-python3-more-itertools_10.5.0-1_all.deb ... Unpacking python3-more-itertools (10.5.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../37-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../38-python3-typeguard_4.4.1-1_all.deb ... Unpacking python3-typeguard (4.4.1-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../39-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../40-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../41-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../42-python3-pkg-resources_75.2.0-1_all.deb ... Unpacking python3-pkg-resources (75.2.0-1) ... Selecting previously unselected package python3-jaraco.text. Preparing to unpack .../43-python3-jaraco.text_4.0.0-1_all.deb ... Unpacking python3-jaraco.text (4.0.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../44-python3-zipp_3.21.0-1_all.deb ... Unpacking python3-zipp (3.21.0-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../45-python3-setuptools_75.2.0-1_all.deb ... Unpacking python3-setuptools (75.2.0-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../46-dh-python_6.20241024_all.deb ... Unpacking dh-python (6.20241024) ... Selecting previously unselected package xml-core. Preparing to unpack .../47-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../48-docutils-common_0.21.2+dfsg-2_all.deb ... Unpacking docutils-common (0.21.2+dfsg-2) ... Selecting previously unselected package fonts-font-awesome. Preparing to unpack .../49-fonts-font-awesome_5.0.10+really4.7.0~dfsg-4.1_all.deb ... Unpacking fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../50-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../51-libjs-underscore_1.13.4~dfsg+~1.11.4-3_all.deb ... Unpacking libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../52-libjs-sphinxdoc_7.4.7-4_all.deb ... Unpacking libjs-sphinxdoc (7.4.7-4) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../53-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package libpython3.13-stdlib:arm64. Preparing to unpack .../54-libpython3.13-stdlib_3.13.0-2_arm64.deb ... Unpacking libpython3.13-stdlib:arm64 (3.13.0-2) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../55-python-babel-localedata_2.16.0-1_all.deb ... Unpacking python-babel-localedata (2.16.0-1) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../56-python3-alabaster_0.7.16-0.1_all.deb ... Unpacking python3-alabaster (0.7.16-0.1) ... Selecting previously unselected package python3.13. Preparing to unpack .../57-python3.13_3.13.0-2_arm64.deb ... Unpacking python3.13 (3.13.0-2) ... Selecting previously unselected package python3-all. Preparing to unpack .../58-python3-all_3.12.7-1_arm64.deb ... Unpacking python3-all (3.12.7-1) ... Selecting previously unselected package python3-asgiref. Preparing to unpack .../59-python3-asgiref_3.8.1-1_all.deb ... Unpacking python3-asgiref (3.8.1-1) ... Selecting previously unselected package python3-babel. Preparing to unpack .../60-python3-babel_2.16.0-1_all.deb ... Unpacking python3-babel (2.16.0-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../61-python3-certifi_2024.8.30+dfsg-1_all.deb ... Unpacking python3-certifi (2024.8.30+dfsg-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../62-python3-chardet_5.2.0+dfsg-1_all.deb ... Unpacking python3-chardet (5.2.0+dfsg-1) ... Selecting previously unselected package python3-charset-normalizer. Preparing to unpack .../63-python3-charset-normalizer_3.4.0-1+b1_arm64.deb ... Unpacking python3-charset-normalizer (3.4.0-1+b1) ... Selecting previously unselected package python3-confusable-homoglyphs. Preparing to unpack .../64-python3-confusable-homoglyphs_3.3.1-1_all.deb ... Unpacking python3-confusable-homoglyphs (3.3.1-1) ... Selecting previously unselected package python3-defusedxml. Preparing to unpack .../65-python3-defusedxml_0.7.1-2_all.deb ... Unpacking python3-defusedxml (0.7.1-2) ... Selecting previously unselected package python3-sqlparse. Preparing to unpack .../66-python3-sqlparse_0.5.2-1_all.deb ... Unpacking python3-sqlparse (0.5.2-1) ... Selecting previously unselected package python3-django. Preparing to unpack .../67-python3-django_3%3a4.2.16-1_all.deb ... Unpacking python3-django (3:4.2.16-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../68-python3-roman_4.2-1_all.deb ... Unpacking python3-roman (4.2-1) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../69-python3-docutils_0.21.2+dfsg-2_all.deb ... Unpacking python3-docutils (0.21.2+dfsg-2) ... Selecting previously unselected package python3-idna. Preparing to unpack .../70-python3-idna_3.8-2_all.deb ... Unpacking python3-idna (3.8-2) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../71-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../72-python3-markupsafe_2.1.5-1+b3_arm64.deb ... Unpacking python3-markupsafe (2.1.5-1+b3) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../73-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../74-python3-packaging_24.2-1_all.deb ... Unpacking python3-packaging (24.2-1) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../75-python3-pygments_2.18.0+dfsg-1_all.deb ... Unpacking python3-pygments (2.18.0+dfsg-1) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../76-python3-urllib3_2.0.7-2_all.deb ... Unpacking python3-urllib3 (2.0.7-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../77-python3-requests_2.32.3+dfsg-1_all.deb ... Unpacking python3-requests (2.32.3+dfsg-1) ... Selecting previously unselected package python3-snowballstemmer. Preparing to unpack .../78-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../79-sphinx-common_7.4.7-4_all.deb ... Unpacking sphinx-common (7.4.7-4) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../80-python3-sphinx_7.4.7-4_all.deb ... Unpacking python3-sphinx (7.4.7-4) ... Selecting previously unselected package sphinx-rtd-theme-common. Preparing to unpack .../81-sphinx-rtd-theme-common_3.0.2+dfsg-1_all.deb ... Unpacking sphinx-rtd-theme-common (3.0.2+dfsg-1) ... Selecting previously unselected package python3-sphinxcontrib.jquery. Preparing to unpack .../82-python3-sphinxcontrib.jquery_4.1-5_all.deb ... Unpacking python3-sphinxcontrib.jquery (4.1-5) ... Selecting previously unselected package python3-sphinx-rtd-theme. Preparing to unpack .../83-python3-sphinx-rtd-theme_3.0.2+dfsg-1_all.deb ... Unpacking python3-sphinx-rtd-theme (3.0.2+dfsg-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:arm64 (1.5.8-1) ... Setting up libkeyutils1:arm64 (1.6.3-4) ... Setting up fonts-lato (2.015-1) ... Setting up libicu72:arm64 (72.1-5+b1) ... Setting up bsdextrautils (2.40.2-11) ... Setting up libmagic-mgc (1:5.45-3+b1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libtirpc-common (1.3.4+ds-1.3) ... Setting up libdebhelper-perl (13.20) ... Setting up libmagic1t64:arm64 (1:5.45-3+b1) ... Setting up gettext-base (0.22.5-2) ... Setting up m4 (1.4.19-4) ... Setting up libcom-err2:arm64 (1.47.1-1+b1) ... Setting up file (1:5.45-3+b1) ... Setting up libelf1t64:arm64 (0.192-4) ... Setting up python-babel-localedata (2.16.0-1) ... Setting up libkrb5support0:arm64 (1.21.3-3) ... Setting up tzdata (2024b-3) ... Current default time zone: 'Etc/UTC' Local time is now: Sun Dec 28 19:17:10 UTC 2025. Universal Time is now: Sun Dec 28 19:17:10 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up libpython3.13-minimal:arm64 (3.13.0-2) ... Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.22.5-2) ... Setting up libk5crypto3:arm64 (1.21.3-3) ... Setting up autoconf (2.72-3) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libuchardet0:arm64 (0.0.8-1+b2) ... Setting up libjson-perl (4.10000-1) ... Setting up python3.13-minimal (3.13.0-2) ... Setting up netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up libkrb5-3:arm64 (1.21.3-3) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up openssl (3.3.2-2) ... Setting up readline-common (8.2-5) ... Setting up libxml2:arm64 (2.12.7+dfsg+really2.9.14-0.2+b1) ... Setting up fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Setting up sphinx-rtd-theme-common (3.0.2+dfsg-1) ... Setting up libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... 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.14.0-1) ... Setting up gettext (0.22.5-2) ... Setting up libtool (2.4.7-8) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 146 added, 0 removed; done. Setting up libgssapi-krb5-2:arm64 (1.21.3-3) ... Setting up libjs-sphinxdoc (7.4.7-4) ... Setting up libreadline8t64:arm64 (8.2-5) ... Setting up dh-strip-nondeterminism (1.14.0-1) ... Setting up groff-base (1.23.0-5) ... Setting up xml-core (0.19) ... Setting up libpython3.13-stdlib:arm64 (3.13.0-2) ... Setting up libtirpc3t64:arm64 (1.3.4+ds-1.3+b1) ... Setting up python3.13 (3.13.0-2) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up man-db (2.13.0-1) ... Not building database; man-db/auto-update is not 'true'. Setting up sphinx-common (7.4.7-4) ... Setting up libnsl2:arm64 (1.3.0-3+b3) ... Setting up libpython3.12-stdlib:arm64 (3.12.7-3) ... Setting up python3.12 (3.12.7-3) ... Setting up debhelper (13.20) ... Setting up libpython3-stdlib:arm64 (3.12.7-1) ... Setting up python3 (3.12.7-1) ... Setting up python3-zipp (3.21.0-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up python3-markupsafe (2.1.5-1+b3) ... Setting up python3-roman (4.2-1) ... Setting up python3-jinja2 (3.1.3-1) ... Setting up python3-packaging (24.2-1) ... Setting up python3-sqlparse (0.5.2-1) ... Setting up python3-certifi (2024.8.30+dfsg-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up python3-idna (3.8-2) ... Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-urllib3 (2.0.7-2) ... Setting up python3-asgiref (3.8.1-1) ... Setting up python3-imagesize (1.4.1-1) ... Setting up python3-more-itertools (10.5.0-1) ... Setting up python3-confusable-homoglyphs (3.3.1-1) ... Setting up python3-django (3:4.2.16-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-defusedxml (0.7.1-2) ... Setting up python3-charset-normalizer (3.4.0-1+b1) ... Setting up python3-alabaster (0.7.16-0.1) ... Setting up python3-typeguard (4.4.1-1) ... Setting up python3-all (3.12.7-1) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-jaraco.text (4.0.0-1) ... Setting up python3-pkg-resources (75.2.0-1) ... Setting up python3-setuptools (75.2.0-1) ... Setting up python3-babel (2.16.0-1) ... update-alternatives: using /usr/bin/pybabel-python3 to provide /usr/bin/pybabel (pybabel) in auto mode Setting up python3-pygments (2.18.0+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-requests (2.32.3+dfsg-1) ... Setting up dh-python (6.20241024) ... Processing triggers for libc-bin (2.40-4) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.21.2+dfsg-2) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.21.2+dfsg-2) ... Setting up python3-sphinx (7.4.7-4) ... Setting up python3-sphinxcontrib.jquery (4.1-5) ... Setting up python3-sphinx-rtd-theme (3.0.2+dfsg-1) ... Processing triggers for ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Writing extended state information... Building tag database... -> Finished parsing the build-deps I: Building the package I: user script /srv/workspace/pbuilder/344925/tmp/hooks/A99_set_merged_usr starting Not re-configuring usrmerge for unstable I: user script /srv/workspace/pbuilder/344925/tmp/hooks/A99_set_merged_usr finished hostname: Name or service not known I: Running cd /build/reproducible-path/python-django-registration-3.3/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-genchanges -S > ../python-django-registration_3.3-1_source.changes dpkg-buildpackage: info: source package python-django-registration dpkg-buildpackage: info: source version 3.3-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Elena Grandi dpkg-source --before-build . dpkg-buildpackage: info: host architecture arm64 debian/rules clean dh clean --with python3,sphinxdoc --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' rm -rf docs/_build/ dh_auto_clean I: pybuild base:311: python3.13 setup.py clean running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.13' does not exist -- can't clean it I: pybuild base:311: python3.12 setup.py clean running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build' (and everything under it) 'build/bdist.linux-aarch64' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.13 setup.py config running config I: pybuild base:311: python3.12 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' cd src/django_registration && /usr/bin/django-admin compilemessages File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_CN/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_TW/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ca/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/hr/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/en/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es_AR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/tr_TR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date. processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fr/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/el/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/he/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt_BR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ar/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/de/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nb/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/it/LC_MESSAGES/django.po” is already compiled and up to date. processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/is/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sr/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/da/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date. cd docs && /usr/bin/make html make[2]: Entering directory '/build/reproducible-path/python-django-registration-3.3/docs' sphinx-build -b html -d _build/doctrees . _build/html Running Sphinx v7.4.7 WARNING: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code. loading translations [en]... done making output directory... done Converting `source_suffix = '.rst'` to `source_suffix = {'.rst': 'restructuredtext'}`. loading intersphinx inventory 'django' from https://docs.djangoproject.com/en/stable/_objects/... loading intersphinx inventory 'python' from https://docs.python.org/3/objects.inv... WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.djangoproject.com/en/stable/_objects/' not fetchable due to : HTTPSConnectionPool(host='docs.djangoproject.com', port=443): Max retries exceeded with url: /en/stable/_objects/ (Caused by NameResolutionError(": Failed to resolve 'docs.djangoproject.com' ([Errno -3] Temporary failure in name resolution)")) WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.python.org' ([Errno -3] Temporary failure in name resolution)")) building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 16 source files that are out of date updating environment: [new config] 16 added, 0 changed, 0 removed reading sources... [ 6%] activation-workflow reading sources... [ 12%] custom-user reading sources... [ 19%] deprecations reading sources... [ 25%] exceptions reading sources... [ 31%] faq reading sources... [ 38%] forms reading sources... [ 44%] index reading sources... [ 50%] install reading sources... [ 56%] one-step-workflow reading sources... [ 62%] quickstart reading sources... [ 69%] security reading sources... [ 75%] settings reading sources... [ 81%] signals reading sources... [ 88%] upgrade reading sources... [ 94%] validators reading sources... [100%] views looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done copying assets... copying static files... done copying extra files... done copying assets: done writing output... [ 6%] activation-workflow writing output... [ 12%] custom-user writing output... [ 19%] deprecations writing output... [ 25%] exceptions writing output... [ 31%] faq writing output... [ 38%] forms writing output... [ 44%] index writing output... [ 50%] install writing output... [ 56%] one-step-workflow writing output... [ 62%] quickstart writing output... [ 69%] security writing output... [ 75%] settings writing output... [ 81%] signals writing output... [ 88%] upgrade writing output... [ 94%] validators writing output... [100%] views generating indices... genindex py-modindex done writing additional pages... search done dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 3 warnings. The HTML pages are in _build/html. Build finished. The HTML pages are in _build/html. make[2]: Leaving directory '/build/reproducible-path/python-django-registration-3.3/docs' dh_auto_build I: pybuild base:311: /usr/bin/python3.13 setup.py build running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation running egg_info creating src/django_registration.egg-info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt writing manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations copying src/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step copying src/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation copying src/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation running egg_info writing src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES copying src/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES copying src/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES copying src/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES copying src/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES copying src/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES copying src/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES copying src/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES copying src/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES copying src/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES copying src/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES copying src/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES copying src/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES copying src/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES copying src/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES copying src/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES copying src/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES copying src/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES copying src/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES copying src/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES copying src/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES copying src/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES copying src/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES copying src/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES copying src/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES copying src/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES copying src/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES copying src/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES copying src/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_auto_test -O--buildsystem=pybuild I: pybuild base:311: cd /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.13 /build/reproducible-path/python-django-registration-3.3/runtests.py Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Found 73 test(s). Operations to perform: Apply all migrations: auth, contenttypes, django_registration, sessions, sites, tests Running migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_registration.0001_initial... OK Applying sessions.0001_initial... OK Applying sites.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Applying tests.0001_initial... OK System check identified no issues (0 silenced). test_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_bad_key) An invalid activation key fails to activate. ... ok test_custom_user_configured (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendViewTests.test_bad_key) An invalid activation key fails to activate. ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendViewTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_registration (tests.base.ActivationTestCase.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.base.ActivationTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.ActivationTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.ActivationTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.base.ActivationTestCase.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.base.ActivationTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.ActivationTestCase.test_registration_signal) ... ok test_case_insensitive_form (tests.test_forms.RegistrationFormTests.test_case_insensitive_form) Test the case-insensitive registration form. ... ok test_case_insensitive_validator (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator) Test the case-insensitive username validator. ... ok test_case_insensitive_validator_eq (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator_eq) Test CaseInsensitiveUnique __eq__ method. ... ok test_confusable_emails (tests.test_forms.RegistrationFormTests.test_confusable_emails) Usernames containing dangerously confusable use of Unicode are ... ok test_confusable_usernames (tests.test_forms.RegistrationFormTests.test_confusable_usernames) Usernames containing dangerously confusable use of Unicode are ... ok test_confusables_email_validator (tests.test_forms.RegistrationFormTests.test_confusables_email_validator) Test the confusable-email validator standalone. ... ok test_confusables_validator (tests.test_forms.RegistrationFormTests.test_confusables_validator) Test the confusable-username validator standalone. ... ok test_custom_reserved_names (tests.test_forms.RegistrationFormTests.test_custom_reserved_names) Reserved names can be overridden by an attribute. ... ok test_email_required (tests.test_forms.RegistrationFormTests.test_email_required) The email address field is required. ... ok test_email_uniqueness (tests.test_forms.RegistrationFormTests.test_email_uniqueness) Email uniqueness is enforced by RegistrationFormUniqueEmail. ... ok test_email_validation (tests.test_forms.RegistrationFormTests.test_email_validation) Stricter-than-RFC email validation is applied. ... ok test_email_validator (tests.test_forms.RegistrationFormTests.test_email_validator) Test the HTMl5 email address validator. ... ok test_reserved_name_non_string (tests.test_forms.RegistrationFormTests.test_reserved_name_non_string) GitHub issue #82: reserved-name validator should not attempt ... ok test_reserved_name_validator_eq (tests.test_forms.RegistrationFormTests.test_reserved_name_validator_eq) Test ReservedNameValidator __eq__ method. ... ok test_reserved_names (tests.test_forms.RegistrationFormTests.test_reserved_names) Reserved names are disallowed. ... ok test_tos_field (tests.test_forms.RegistrationFormTests.test_tos_field) The terms-of-service field on RegistrationFormTermsOfService ... ok test_username_uniqueness (tests.test_forms.RegistrationFormTests.test_username_uniqueness) Username uniqueness is enforced. ... ok test_custom_user_configured (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_signal) ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_signal) ... ok test_registration (tests.base.WorkflowTestCase.test_registration) Registration creates a new account. ... ok test_registration_closed (tests.base.WorkflowTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.WorkflowTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.WorkflowTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.base.WorkflowTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.WorkflowTestCase.test_registration_signal) ... ok test_activation (tests.test_views.ActivationViewTests.test_activation) Activation of an account functions properly when using a ... ok test_user_mismatch_breaks_view (tests.test_views.CustomUserTests.test_user_mismatch_breaks_view) When RegistrationView detects a mismatch between the model used by ... ok test_sensitive_post_parameters_are_filtered (tests.test_views.SensitiveParameterFilterTests.test_sensitive_post_parameters_are_filtered) When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- Ran 73 tests in 10.725s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... I: pybuild base:311: cd /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.12 /build/reproducible-path/python-django-registration-3.3/runtests.py Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Found 73 test(s). Operations to perform: Apply all migrations: auth, contenttypes, django_registration, sessions, sites, tests Running migrations: Applying contenttypes.0001_initial... OK Applying contenttypes.0002_remove_content_type_name... OK Applying auth.0001_initial... OK Applying auth.0002_alter_permission_name_max_length... OK Applying auth.0003_alter_user_email_max_length... OK Applying auth.0004_alter_user_username_opts... OK Applying auth.0005_alter_user_last_login_null... OK Applying auth.0006_require_contenttypes_0002... OK Applying auth.0007_alter_validators_add_error_messages... OK Applying auth.0008_alter_user_username_max_length... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_registration.0001_initial... OK Applying sessions.0001_initial... OK Applying sites.0001_initial... OK Applying sites.0002_alter_domain_unique... OK Applying tests.0001_initial... OK System check identified no issues (0 silenced). test_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_bad_key) An invalid activation key fails to activate. ... ok test_custom_user_configured (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendCustomUserTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_activation) Activation of an account functions properly. ... ok test_activation_expired (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_expired) An expired account can't be activated. ... ok test_activation_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_activation_signal) ... ok test_bad_key (tests.test_activation_workflow.ActivationBackendViewTests.test_bad_key) An invalid activation key fails to activate. ... ok test_nonexistent_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_nonexistent_activation) A nonexistent username in an activation key will fail to ... ok test_registration (tests.test_activation_workflow.ActivationBackendViewTests.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_activation_workflow.ActivationBackendViewTests.test_registration_signal) ... ok test_repeat_activation (tests.test_activation_workflow.ActivationBackendViewTests.test_repeat_activation) Once activated, attempting to re-activate an account (even ... ok test_registration (tests.base.ActivationTestCase.test_registration) Registration creates a new inactive account and sends an ... ok test_registration_closed (tests.base.ActivationTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.ActivationTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.ActivationTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_no_sites (tests.base.ActivationTestCase.test_registration_no_sites) Registration still functions properly when ... ok test_registration_open (tests.base.ActivationTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.ActivationTestCase.test_registration_signal) ... ok test_case_insensitive_form (tests.test_forms.RegistrationFormTests.test_case_insensitive_form) Test the case-insensitive registration form. ... ok test_case_insensitive_validator (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator) Test the case-insensitive username validator. ... ok test_case_insensitive_validator_eq (tests.test_forms.RegistrationFormTests.test_case_insensitive_validator_eq) Test CaseInsensitiveUnique __eq__ method. ... ok test_confusable_emails (tests.test_forms.RegistrationFormTests.test_confusable_emails) Usernames containing dangerously confusable use of Unicode are ... ok test_confusable_usernames (tests.test_forms.RegistrationFormTests.test_confusable_usernames) Usernames containing dangerously confusable use of Unicode are ... ok test_confusables_email_validator (tests.test_forms.RegistrationFormTests.test_confusables_email_validator) Test the confusable-email validator standalone. ... ok test_confusables_validator (tests.test_forms.RegistrationFormTests.test_confusables_validator) Test the confusable-username validator standalone. ... ok test_custom_reserved_names (tests.test_forms.RegistrationFormTests.test_custom_reserved_names) Reserved names can be overridden by an attribute. ... ok test_email_required (tests.test_forms.RegistrationFormTests.test_email_required) The email address field is required. ... ok test_email_uniqueness (tests.test_forms.RegistrationFormTests.test_email_uniqueness) Email uniqueness is enforced by RegistrationFormUniqueEmail. ... ok test_email_validation (tests.test_forms.RegistrationFormTests.test_email_validation) Stricter-than-RFC email validation is applied. ... ok test_email_validator (tests.test_forms.RegistrationFormTests.test_email_validator) Test the HTMl5 email address validator. ... ok test_reserved_name_non_string (tests.test_forms.RegistrationFormTests.test_reserved_name_non_string) GitHub issue #82: reserved-name validator should not attempt ... ok test_reserved_name_validator_eq (tests.test_forms.RegistrationFormTests.test_reserved_name_validator_eq) Test ReservedNameValidator __eq__ method. ... ok test_reserved_names (tests.test_forms.RegistrationFormTests.test_reserved_names) Reserved names are disallowed. ... ok test_tos_field (tests.test_forms.RegistrationFormTests.test_tos_field) The terms-of-service field on RegistrationFormTermsOfService ... ok test_username_uniqueness (tests.test_forms.RegistrationFormTests.test_username_uniqueness) Username uniqueness is enforced. ... ok test_custom_user_configured (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_custom_user_configured) Asserts that the user model in use is the custom user model ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowCustomUserTests.test_registration_signal) ... ok test_registration (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration) Registration creates a new account and logs the user in. ... ok test_registration_closed (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.test_one_step_workflow.OneStepWorkflowViewTests.test_registration_signal) ... ok test_registration (tests.base.WorkflowTestCase.test_registration) Registration creates a new account. ... ok test_registration_closed (tests.base.WorkflowTestCase.test_registration_closed) ``REGISTRATION_OPEN``, when ``False``, disallows registration. ... ok test_registration_failure (tests.base.WorkflowTestCase.test_registration_failure) Registering with invalid data fails. ... ok test_registration_get (tests.base.WorkflowTestCase.test_registration_get) HTTP ``GET`` to the registration view uses the appropriate ... ok test_registration_open (tests.base.WorkflowTestCase.test_registration_open) ``REGISTRATION_OPEN``, when ``True``, permits registration. ... ok test_registration_signal (tests.base.WorkflowTestCase.test_registration_signal) ... ok test_activation (tests.test_views.ActivationViewTests.test_activation) Activation of an account functions properly when using a ... ok test_user_mismatch_breaks_view (tests.test_views.CustomUserTests.test_user_mismatch_breaks_view) When RegistrationView detects a mismatch between the model used by ... ok test_sensitive_post_parameters_are_filtered (tests.test_views.SensitiveParameterFilterTests.test_sensitive_post_parameters_are_filtered) When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- Ran 73 tests in 10.231s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild debian/rules override_dh_auto_install make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' # dh_auto_install expects the following directory to exist (before it # is created?) mkdir -p debian/python-django-registration-doc dh_auto_install I: pybuild base:311: /usr/bin/python3.13 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration 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 src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.__pycache__' to be distributed and are already explicitly excluding 'django_registration.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.activation.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.activation.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.activation.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.activation.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.activation.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.one_step.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.one_step.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.one_step.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.one_step.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.one_step.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.migrations.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.migrations.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.migrations.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.migrations.__pycache__' to be distributed and are already explicitly excluding 'django_registration.migrations.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__ copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.13_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/activation/views.py to views.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/one_step/views.py to views.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/backends/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/__init__.py to __init__.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/exceptions.py to exceptions.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/forms.py to forms.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/signals.py to signals.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/validators.py to validators.cpython-313.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/views.py to views.cpython-313.pyc running install_egg_info Copying src/django_registration.egg-info to /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration-3.3.egg-info Skipping SOURCES.txt running install_scripts I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration 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 src/django_registration.egg-info/PKG-INFO writing dependency_links to src/django_registration.egg-info/dependency_links.txt writing requirements to src/django_registration.egg-info/requires.txt writing top-level names to src/django_registration.egg-info/top_level.txt reading manifest file 'src/django_registration.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/django_registration.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.__pycache__' to be distributed and are already explicitly excluding 'django_registration.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.activation.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.activation.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.activation.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.activation.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.activation.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.backends.one_step.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.backends.one_step.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.backends.one_step.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.backends.one_step.__pycache__' to be distributed and are already explicitly excluding 'django_registration.backends.one_step.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_registration.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'django_registration.migrations.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_registration.migrations.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_registration.migrations.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_registration.migrations.__pycache__' to be distributed and are already explicitly excluding 'django_registration.migrations.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__ copying src/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES copying src/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/validators.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/validators.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/signals.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/signals.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/forms.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/forms.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/exceptions.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/exceptions.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_TW/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/sl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pt/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ko/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ja/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/is/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/hr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/he/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/da/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ca/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/bg/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.po -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar/LC_MESSAGES/django.mo -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/one_step/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-313.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-312.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/activation/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/one_step/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/backends/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/exceptions.py to exceptions.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/forms.py to forms.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/signals.py to signals.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/validators.py to validators.cpython-312.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/views.py to views.cpython-312.pyc running install_egg_info Copying src/django_registration.egg-info to /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration-3.3.egg-info Skipping SOURCES.txt running install_scripts # Drop .po files and keep only .mo files (compiled) find debian/python3-django-registration/ -name '*.po' -exec rm -v {} \; ; find debian/python-django-registration-doc/ -name '*.po' -exec rm -v {} \; ; removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.12/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.13/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' make[1]: Leaving directory '/build/reproducible-path/python-django-registration-3.3' dh_installdocs -O--buildsystem=pybuild dh_installdocs: warning: Cannot auto-detect main package for python-django-registration-doc. If the default is wrong, please use --doc-main-package dh_sphinxdoc -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 Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/it/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/is/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/he/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/en/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/el/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/de/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/da/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.mo 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 dpkg-gencontrol: warning: Depends field of package python3-django-registration: substitution variable ${sphinxdoc:Depends} used, but is not defined dpkg-gencontrol: warning: package python-django-registration-doc: substitution variable ${sphinxdoc:Built-Using} unused, but is defined dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-django-registration' in '../python3-django-registration_3.3-1_all.deb'. dpkg-deb: building package 'python-django-registration-doc' in '../python-django-registration-doc_3.3-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python-django-registration_3.3-1_arm64.buildinfo dpkg-genchanges --build=binary -O../python-django-registration_3.3-1_arm64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration I: user script /srv/workspace/pbuilder/344925/tmp/hooks/B01_cleanup starting I: user script /srv/workspace/pbuilder/344925/tmp/hooks/B01_cleanup finished I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /srv/workspace/pbuilder/344925 and its subdirectories I: Current time: Mon Dec 29 09:18:23 +14 2025 I: pbuilder-time-stamp: 1766949503 + false + set +x Sun Dec 28 19:18:23 UTC 2025 I: Signing ./b2/python-django-registration_3.3-1_arm64.buildinfo as python-django-registration_3.3-1_arm64.buildinfo.asc Sun Dec 28 19:18:23 UTC 2025 I: Signed ./b2/python-django-registration_3.3-1_arm64.buildinfo as ./b2/python-django-registration_3.3-1_arm64.buildinfo.asc Sun Dec 28 19:18:23 UTC 2025 - build #2 for python-django-registration/unstable/arm64 on codethink01-arm64 done. Starting cleanup. All cleanup done. Sun Dec 28 19:18:23 UTC 2025 - reproducible_build.sh stopped running as /tmp/jenkins-script-r5zJBFI2, removing. /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy: total 548 drwxr-xr-x 2 jenkins jenkins 4096 Nov 25 12:53 b1 drwxr-xr-x 2 jenkins jenkins 4096 Nov 25 12:55 b2 -rw-r--r-- 1 jenkins jenkins 2355 Oct 24 2022 python-django-registration_3.3-1.dsc -rw------- 1 jenkins jenkins 543655 Nov 25 12:53 rbuildlog.zwAjPsW /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1: total 764 -rw-r--r-- 1 jenkins jenkins 539765 Nov 25 12:53 build.log -rw-r--r-- 1 jenkins jenkins 64268 Nov 25 12:53 python-django-registration-doc_3.3-1_all.deb -rw-r--r-- 1 jenkins jenkins 10396 Nov 25 12:53 python-django-registration_3.3-1.debian.tar.xz -rw-r--r-- 1 jenkins jenkins 2355 Nov 25 12:53 python-django-registration_3.3-1.dsc -rw-r--r-- 1 jenkins jenkins 7649 Nov 25 12:53 python-django-registration_3.3-1_arm64.buildinfo -rw-r--r-- 1 jenkins jenkins 8531 Nov 25 12:53 python-django-registration_3.3-1_arm64.buildinfo.asc -rw-r--r-- 1 jenkins jenkins 2047 Nov 25 12:53 python-django-registration_3.3-1_arm64.changes -rw-r--r-- 1 jenkins jenkins 2403 Nov 25 12:53 python-django-registration_3.3-1_source.changes -rw-r--r-- 1 jenkins jenkins 85046 Nov 25 12:53 python-django-registration_3.3.orig.tar.gz -rw-r--r-- 1 jenkins jenkins 833 Nov 25 12:53 python-django-registration_3.3.orig.tar.gz.asc -rw-r--r-- 1 jenkins jenkins 26504 Nov 25 12:53 python3-django-registration_3.3-1_all.deb /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2: total 756 -rw-r--r-- 1 jenkins jenkins 541700 Nov 25 12:55 build.log -rw-r--r-- 1 jenkins jenkins 64268 Nov 25 12:55 python-django-registration-doc_3.3-1_all.deb -rw-r--r-- 1 jenkins jenkins 10396 Nov 25 12:55 python-django-registration_3.3-1.debian.tar.xz -rw-r--r-- 1 jenkins jenkins 2355 Nov 25 12:55 python-django-registration_3.3-1.dsc -rw-r--r-- 1 jenkins jenkins 7649 Nov 25 12:55 python-django-registration_3.3-1_arm64.buildinfo -rw-r--r-- 1 jenkins jenkins 8531 Nov 25 12:55 python-django-registration_3.3-1_arm64.buildinfo.asc -rw-r--r-- 1 jenkins jenkins 2047 Nov 25 12:55 python-django-registration_3.3-1_arm64.changes -rw-r--r-- 1 jenkins jenkins 2403 Nov 25 12:55 python-django-registration_3.3-1_source.changes -rw-r--r-- 1 jenkins jenkins 85046 Nov 25 12:55 python-django-registration_3.3.orig.tar.gz -rw-r--r-- 1 jenkins jenkins 833 Nov 25 12:55 python-django-registration_3.3.orig.tar.gz.asc -rw-r--r-- 1 jenkins jenkins 26504 Nov 25 12:55 python3-django-registration_3.3-1_all.deb Mon Nov 25 12:55:24 UTC 2024 I: Deleting $TMPDIR on codethink01-arm64.debian.net. Mon Nov 25 12:55:25 UTC 2024 I: python-django-registration_3.3-1_arm64.changes: Format: 1.8 Date: Mon, 24 Oct 2022 13:30:38 +0200 Source: python-django-registration Binary: python-django-registration-doc python3-django-registration Architecture: all Version: 3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Elena Grandi Description: python-django-registration-doc - User-registration application for Django (Documentation) python3-django-registration - User-registration application for Django (Python 3) Changes: python-django-registration (3.3-1) unstable; urgency=medium . * Team upload. . [ Stefano Rivera ] * New upstream release. * Drop all patches, superseded upstream. * Bump copyright years. * Adjust paths to build tools. * Run test suite on all supported Python 3 versions. * New Build-Depends: python3-confusable-homoglyphs. . [ Elena Grandi ] * Bump standards-version (no changes needed). * Bump compat level. * Lintian fixes. * Removed unnecessary signatures from the upstream key. * Added UMEGAYA. Checksums-Sha1: edd1964175a6abf707589bb7bffc4b9f0ae9e2de 64268 python-django-registration-doc_3.3-1_all.deb 751c2a48b16a1f76564083f70e3cfec4c6a7229e 7649 python-django-registration_3.3-1_arm64.buildinfo 3a01356f54cfe53ac905b6238ca895b44a916721 26504 python3-django-registration_3.3-1_all.deb Checksums-Sha256: 24c119f3d26878e03064f60da4d1ea7f9cad8044f7f990eb51dbfb1987a4356c 64268 python-django-registration-doc_3.3-1_all.deb a723eee4011d5cb886de06ad463077574e0e9115f329b9a7d133120d1a7dcdc7 7649 python-django-registration_3.3-1_arm64.buildinfo e8762483f0baaa01891ab1bf73d3aa6b093a0ef9e76753592b343e51011cdea3 26504 python3-django-registration_3.3-1_all.deb Files: 598e88d13e8be75eaebb6116f7f427f9 64268 doc optional python-django-registration-doc_3.3-1_all.deb 4168a157a1e57558efa8385a8fa0daf8 7649 python optional python-django-registration_3.3-1_arm64.buildinfo f79da654b004c7efeaa70027ada2e593 26504 python optional python3-django-registration_3.3-1_all.deb removed '/var/lib/jenkins/userContent/reproducible/debian/rbuild/unstable/arm64/python-django-registration_3.3-1.rbuild.log' removed '/var/lib/jenkins/userContent/reproducible/debian/rbuild/unstable/arm64/python-django-registration_3.3-1.rbuild.log.gz' removed '/var/lib/jenkins/userContent/reproducible/debian/logs/unstable/arm64/python-django-registration_3.3-1.build1.log.gz' removed '/var/lib/jenkins/userContent/reproducible/debian/logs/unstable/arm64/python-django-registration_3.3-1.build2.log.gz' removed '/var/lib/jenkins/userContent/reproducible/debian/buildinfo/unstable/arm64/python-django-registration_3.3-1_arm64.buildinfo' removed '/var/lib/jenkins/userContent/reproducible/debian/logdiffs/unstable/arm64/python-django-registration_3.3-1.diff.gz' Diff of the two buildlogs: -- --- b1/build.log 2024-11-25 12:53:47.278056643 +0000 +++ b2/build.log 2024-11-25 12:55:24.173707317 +0000 @@ -1,6 +1,6 @@ I: pbuilder: network access will be disabled during build -I: Current time: Mon Nov 25 00:52:15 -12 2024 -I: pbuilder-time-stamp: 1732539135 +I: Current time: Mon Dec 29 09:16:50 +14 2025 +I: pbuilder-time-stamp: 1766949410 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: copying local configuration @@ -26,52 +26,84 @@ dpkg-source: info: unpacking python-django-registration_3.3-1.debian.tar.xz I: Not using root during the build. I: Installing the build-deps -I: user script /srv/workspace/pbuilder/3825326/tmp/hooks/D02_print_environment starting +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D01_modify_environment starting +debug: Running on codethink01-arm64. +I: Changing host+domainname to test build reproducibility +I: Adding a custom variable just for the fun of it... +I: Changing /bin/sh to bash +'/bin/sh' -> '/bin/bash' +lrwxrwxrwx 1 root root 9 Dec 28 19:16 /bin/sh -> /bin/bash +I: Setting pbuilder2's login shell to /bin/bash +I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D01_modify_environment finished +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D02_print_environment starting I: set - BUILDDIR='/build/reproducible-path' - BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' - BUILDUSERNAME='pbuilder1' - BUILD_ARCH='arm64' - DEBIAN_FRONTEND='noninteractive' + BASH=/bin/sh + BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:globskipdots:hostcomplete:interactive_comments:patsub_replacement:progcomp:promptvars:sourcepath + BASH_ALIASES=() + BASH_ARGC=() + BASH_ARGV=() + BASH_CMDS=() + BASH_LINENO=([0]="12" [1]="0") + BASH_LOADABLES_PATH=/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib/bash:. + BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") + BASH_VERSINFO=([0]="5" [1]="2" [2]="32" [3]="1" [4]="release" [5]="aarch64-unknown-linux-gnu") + BASH_VERSION='5.2.32(1)-release' + BUILDDIR=/build/reproducible-path + BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' + BUILDUSERNAME=pbuilder2 + BUILD_ARCH=arm64 + DEBIAN_FRONTEND=noninteractive DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=12 ' - DISTRIBUTION='unstable' - HOME='/root' - HOST_ARCH='arm64' + DIRSTACK=() + DISTRIBUTION=unstable + EUID=0 + FUNCNAME=([0]="Echo" [1]="main") + GROUPS=() + HOME=/root + HOSTNAME=i-capture-the-hostname + HOSTTYPE=aarch64 + HOST_ARCH=arm64 IFS=' ' - INVOCATION_ID='0e0b7970444f480989ce537bf542d0e0' - LANG='C' - LANGUAGE='en_US:en' - LC_ALL='C' - MAIL='/var/mail/root' - OPTIND='1' - PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' - PBCURRENTCOMMANDLINEOPERATION='build' - PBUILDER_OPERATION='build' - PBUILDER_PKGDATADIR='/usr/share/pbuilder' - PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' - PBUILDER_SYSCONFDIR='/etc' - PPID='3825326' - PS1='# ' - PS2='> ' + INVOCATION_ID=4dc1c65e81b64066bd9fd00344cfc6c5 + LANG=C + LANGUAGE=nl_BE:nl + LC_ALL=C + MACHTYPE=aarch64-unknown-linux-gnu + MAIL=/var/mail/root + OPTERR=1 + OPTIND=1 + OSTYPE=linux-gnu + PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path + PBCURRENTCOMMANDLINEOPERATION=build + PBUILDER_OPERATION=build + PBUILDER_PKGDATADIR=/usr/share/pbuilder + PBUILDER_PKGLIBDIR=/usr/lib/pbuilder + PBUILDER_SYSCONFDIR=/etc + PIPESTATUS=([0]="0") + POSIXLY_CORRECT=y + PPID=344925 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.SUQ9kGBy/pbuilderrc_acZp --distribution unstable --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1 --logfile b1/build.log python-django-registration_3.3-1.dsc' - SUDO_GID='109' - SUDO_UID='104' - SUDO_USER='jenkins' - TERM='unknown' - TZ='/usr/share/zoneinfo/Etc/GMT+12' - USER='root' - _='/usr/bin/systemd-run' - http_proxy='http://192.168.101.4:3128' + PWD=/ + SHELL=/bin/bash + SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix + SHLVL=3 + SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/pbuilderrc_djor --distribution unstable --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/unstable-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2 --logfile b2/build.log python-django-registration_3.3-1.dsc' + SUDO_GID=109 + SUDO_UID=104 + SUDO_USER=jenkins + TERM=unknown + TZ=/usr/share/zoneinfo/Etc/GMT-14 + UID=0 + USER=root + _='I: set' + http_proxy=http://192.168.101.4:3128 I: uname -a - Linux codethink02-arm64 6.1.0-28-cloud-arm64 #1 SMP Debian 6.1.119-1 (2024-11-22) aarch64 GNU/Linux + Linux i-capture-the-hostname 6.1.0-28-cloud-arm64 #1 SMP Debian 6.1.119-1 (2024-11-22) aarch64 GNU/Linux I: ls -l /bin - lrwxrwxrwx 1 root root 7 Nov 22 14:40 /bin -> usr/bin -I: user script /srv/workspace/pbuilder/3825326/tmp/hooks/D02_print_environment finished + lrwxrwxrwx 1 root root 7 Nov 22 2024 /bin -> usr/bin +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy @@ -227,7 +259,7 @@ Get: 104 http://deb.debian.org/debian unstable/main arm64 sphinx-rtd-theme-common all 3.0.2+dfsg-1 [1023 kB] Get: 105 http://deb.debian.org/debian unstable/main arm64 python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 106 http://deb.debian.org/debian unstable/main arm64 python3-sphinx-rtd-theme all 3.0.2+dfsg-1 [29.5 kB] -Fetched 51.6 MB in 0s (189 MB/s) +Fetched 51.6 MB in 0s (175 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package fonts-lato. (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 ... 20083 files and directories currently installed.) @@ -581,8 +613,8 @@ Setting up tzdata (2024b-3) ... Current default time zone: 'Etc/UTC' -Local time is now: Mon Nov 25 12:52:36 UTC 2024. -Universal Time is now: Mon Nov 25 12:52:36 UTC 2024. +Local time is now: Sun Dec 28 19:17:10 UTC 2025. +Universal Time is now: Sun Dec 28 19:17:10 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up libpython3.13-minimal:arm64 (3.13.0-2) ... @@ -690,7 +722,11 @@ Building tag database... -> Finished parsing the build-deps I: Building the package -I: Running cd /build/reproducible-path/python-django-registration-3.3/ && 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 > ../python-django-registration_3.3-1_source.changes +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/A99_set_merged_usr starting +Not re-configuring usrmerge for unstable +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/A99_set_merged_usr finished +hostname: Name or service not known +I: Running cd /build/reproducible-path/python-django-registration-3.3/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-genchanges -S > ../python-django-registration_3.3-1_source.changes dpkg-buildpackage: info: source package python-django-registration dpkg-buildpackage: info: source version 3.3-1 dpkg-buildpackage: info: source distribution unstable @@ -728,36 +764,36 @@ debian/rules override_dh_auto_build make[1]: Entering directory '/build/reproducible-path/python-django-registration-3.3' cd src/django_registration && /usr/bin/django-admin compilemessages -processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fr/LC_MESSAGES -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nb/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/da/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_CN/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_TW/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ca/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/hr/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/en/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es_AR/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/tr_TR/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/de/LC_MESSAGES/django.po” is already compiled and up to date. +processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fr/LC_MESSAGES +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/el/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/he/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt_BR/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ar/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/de/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nb/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/it/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/is/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_TW/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date. +processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es/LC_MESSAGES File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/en/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ca/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/zh_CN/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/he/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/el/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/is/LC_MESSAGES/django.po” is already compiled and up to date. File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/sr/LC_MESSAGES/django.po” is already compiled and up to date. -processing file django.po in /build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es/LC_MESSAGES -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ar/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/es_AR/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/hr/LC_MESSAGES/django.po” is already compiled and up to date. -File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/da/LC_MESSAGES/django.po” is already compiled and up to date. +File “/build/reproducible-path/python-django-registration-3.3/src/django_registration/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date. cd docs && /usr/bin/make html make[2]: Entering directory '/build/reproducible-path/python-django-registration-3.3/docs' sphinx-build -b html -d _build/doctrees . _build/html @@ -769,9 +805,9 @@ loading intersphinx inventory 'django' from https://docs.djangoproject.com/en/stable/_objects/... loading intersphinx inventory 'python' from https://docs.python.org/3/objects.inv... WARNING: failed to reach any of the inventories with the following issues: -intersphinx inventory 'https://docs.djangoproject.com/en/stable/_objects/' not fetchable due to : HTTPSConnectionPool(host='docs.djangoproject.com', port=443): Max retries exceeded with url: /en/stable/_objects/ (Caused by NameResolutionError(": Failed to resolve 'docs.djangoproject.com' ([Errno -3] Temporary failure in name resolution)")) +intersphinx inventory 'https://docs.djangoproject.com/en/stable/_objects/' not fetchable due to : HTTPSConnectionPool(host='docs.djangoproject.com', port=443): Max retries exceeded with url: /en/stable/_objects/ (Caused by NameResolutionError(": Failed to resolve 'docs.djangoproject.com' ([Errno -3] Temporary failure in name resolution)")) WARNING: failed to reach any of the inventories with the following issues: -intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.python.org' ([Errno -3] Temporary failure in name resolution)")) +intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.python.org' ([Errno -3] Temporary failure in name resolution)")) building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 16 source files that are out of date @@ -3703,7 +3739,7 @@ When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- -Ran 73 tests in 10.188s +Ran 73 tests in 10.725s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... @@ -3873,7 +3909,7 @@ When an unexpected exception occurs during a POST request to the ... ok ---------------------------------------------------------------------- -Ran 73 tests in 10.306s +Ran 73 tests in 10.231s OK Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... @@ -7348,43 +7384,43 @@ dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/it/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/is/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/he/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/es/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/en/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/el/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/de/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/da/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.mo - Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.mo Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/de/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/da/LC_MESSAGES/django.mo + Normalized debian/python3-django-registration/usr/lib/python3/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.mo 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 -dpkg-gencontrol: warning: package python-django-registration-doc: substitution variable ${sphinxdoc:Built-Using} unused, but is defined dpkg-gencontrol: warning: Depends field of package python3-django-registration: substitution variable ${sphinxdoc:Depends} used, but is not defined +dpkg-gencontrol: warning: package python-django-registration-doc: substitution variable ${sphinxdoc:Built-Using} unused, but is defined dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-django-registration' in '../python3-django-registration_3.3-1_all.deb'. @@ -7396,12 +7432,14 @@ dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/B01_cleanup starting +I: user script /srv/workspace/pbuilder/344925/tmp/hooks/B01_cleanup finished I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env -I: removing directory /srv/workspace/pbuilder/3825326 and its subdirectories -I: Current time: Mon Nov 25 00:53:46 -12 2024 -I: pbuilder-time-stamp: 1732539226 +I: removing directory /srv/workspace/pbuilder/344925 and its subdirectories +I: Current time: Mon Dec 29 09:18:23 +14 2025 +I: pbuilder-time-stamp: 1766949503 Compressing the 2nd log... /var/lib/jenkins/userContent/reproducible/debian/logdiffs/unstable/arm64/python-django-registration_3.3-1.diff: 82.9% -- replaced with /var/lib/jenkins/userContent/reproducible/debian/logdiffs/unstable/arm64/python-django-registration_3.3-1.diff.gz b2/build.log: 95.1% -- replaced with stdout Compressing the 1st log... b1/build.log: 95.3% -- replaced with stdout Mon Nov 25 12:55:26 UTC 2024 I: diffoscope 283 will be used to compare the two builds: ++ date -u +%s + DIFFOSCOPE_STAMP=/var/log/reproducible-builds/diffoscope_stamp_python-django-registration_unstable_arm64_1732539326 + touch /var/log/reproducible-builds/diffoscope_stamp_python-django-registration_unstable_arm64_1732539326 + RESULT=0 + systemd-run '--description=diffoscope on python-django-registration/3.3-1 in unstable/arm64' --slice=rb-build-diffoscope.slice -u rb-diffoscope-arm64_16-38213 '--property=SuccessExitStatus=1 124' --user --send-sighup --pipe --wait -E TMPDIR timeout 155m nice schroot --directory /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy --run-session -c jenkins-reproducible-unstable-diffoscope-3fdb429e-89a3-41df-94fd-83fdb9e265dd -- sh -c 'export TMPDIR=/srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/dbd-tmp-a8d8mp9 ; timeout 150m diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/python-django-registration_3.3-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/python-django-registration_3.3-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/python-django-registration_3.3-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1/python-django-registration_3.3-1_arm64.changes /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2/python-django-registration_3.3-1_arm64.changes' + false + set +x Running as unit: rb-diffoscope-arm64_16-38213.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/python-django-registration_3.3-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/python-django-registration_3.3-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/python-django-registration_3.3-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b1/python-django-registration_3.3-1_arm64.changes /srv/reproducible-results/rbuild-debian/r-b-build.SUQ9kGBy/b2/python-django-registration_3.3-1_arm64.changes ## command (total time: 0.000s) 0.000s 1 call cmp (internal) ## has_same_content_as (total time: 0.000s) 0.000s 1 call abc.DotChangesFile ## main (total time: 0.450s) 0.450s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.024s) 0.024s 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: 867ms CPU time consumed: 866ms _ _ _ _ _ __ _ _| |_| |__ ___ _ __ __| |(_) __ _ _ __ __ _ ___ | '_ \| | | | __| '_ \ / _ \| '_ \ _____ / _` || |/ _` | '_ \ / _` |/ _ \ | |_) | |_| | |_| | | | (_) | | | |_____| (_| || | (_| | | | | (_| | (_) | | .__/ \__, |\__|_| |_|\___/|_| |_| \__,_|/ |\__,_|_| |_|\__, |\___/ |_| |___/ |__/ |___/ _ _ _ _ _ __ ___ __ _(_)___| |_ _ __ __ _| |_(_) ___ _ __ _____| '__/ _ \/ _` | / __| __| '__/ _` | __| |/ _ \| '_ \ |_____| | | __/ (_| | \__ \ |_| | | (_| | |_| | (_) | | | | |_| \___|\__, |_|___/\__|_| \__,_|\__|_|\___/|_| |_| |___/ Mon Nov 25 12:55:27 UTC 2024 I: diffoscope 283 found no differences in the changes files, and a .buildinfo file also exists. Mon Nov 25 12:55:27 UTC 2024 I: python-django-registration from unstable built successfully and reproducibly on arm64. INSERT 0 1 INSERT 0 1 DELETE 1 [2024-11-25 12:55:28] INFO: Starting at 2024-11-25 12:55:28.249665 [2024-11-25 12:55:28] INFO: Generating the pages of 1 package(s) [2024-11-25 12:55:28] CRITICAL: https://tests.reproducible-builds.org/debian/unstable/arm64/python-django-registration didn't produce a buildlog, even though it has been built. [2024-11-25 12:55:28] INFO: Finished at 2024-11-25 12:55:28.879436, took: 0:00:00.629785 Mon Nov 25 12:55:28 UTC 2024 - successfully updated the database and updated https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/python-django-registration.html Mon Nov 25 12:55:28 UTC 2024 I: Submitting .buildinfo files to external archives: Mon Nov 25 12:55:29 UTC 2024 I: Submitting 12K b1/python-django-registration_3.3-1_arm64.buildinfo.asc https://buildinfo.debian.net/751c2a48b16a1f76564083f70e3cfec4c6a7229e/python-django-registration_3.3-1_all Mon Nov 25 12:55:29 UTC 2024 I: Submitting 12K b2/python-django-registration_3.3-1_arm64.buildinfo.asc https://buildinfo.debian.net/bb3ff2881e56e03d675cba3fc12044294f7f1f96/python-django-registration_3.3-1_all Mon Nov 25 12:55:30 UTC 2024 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Mon Nov 25 12:55:30 UTC 2024 I: Done submitting .buildinfo files. Mon Nov 25 12:55:30 UTC 2024 I: Removing signed python-django-registration_3.3-1_arm64.buildinfo.asc files: removed './b1/python-django-registration_3.3-1_arm64.buildinfo.asc' removed './b2/python-django-registration_3.3-1_arm64.buildinfo.asc' 1732539330 arm64 unstable python-django-registration Starting cleanup. /var/lib/jenkins/userContent/reproducible/debian/rbuild/unstable/arm64/python-django-registration_3.3-1.rbuild.log: 94.7% -- replaced with /var/lib/jenkins/userContent/reproducible/debian/rbuild/unstable/arm64/python-django-registration_3.3-1.rbuild.log.gz [2024-11-25 12:55:31] INFO: Starting at 2024-11-25 12:55:31.101632 [2024-11-25 12:55:31] INFO: Generating the pages of 1 package(s) [2024-11-25 12:55:31] INFO: Finished at 2024-11-25 12:55:31.676565, took: 0:00:00.574943 All cleanup done. Mon Nov 25 12:55:31 UTC 2024 - total duration: 0h 3m 23s. Mon Nov 25 12:55:31 UTC 2024 - reproducible_build.sh stopped running as /tmp/jenkins-script-60GYEpoh, removing. Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 3min 27.877s CPU time consumed: 8.476s