Thu May 9 09:25:54 UTC 2024 I: starting to build python-django-registration/trixie/armhf on jenkins on '2024-05-09 09:25' Thu May 9 09:25:54 UTC 2024 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/armhf_30/3802/console.log Thu May 9 09:25:54 UTC 2024 I: Downloading source for trixie/python-django-registration=3.3-1 --2024-05-09 09:25:54-- 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% 264M=0s 2024-05-09 09:25:54 (264 MB/s) - ‘python-django-registration_3.3-1.dsc’ saved [2355/2355] Thu May 9 09:25:54 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----- Thu May 9 09:25:54 UTC 2024 I: Checking whether the package is not for us Thu May 9 09:25:54 UTC 2024 I: Starting 1st build on remote node ff64a-armhf-rb.debian.net. Thu May 9 09:25:54 UTC 2024 I: Preparing to do remote build '1' on ff64a-armhf-rb.debian.net. Thu May 9 09:35:05 UTC 2024 I: Deleting $TMPDIR on ff64a-armhf-rb.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Wed May 8 21:26:03 -12 2024 I: pbuilder-time-stamp: 1715246763 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/trixie-reproducible-base.tgz] I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Copying source file I: copying [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/25098/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='armhf' DEBIAN_FRONTEND='noninteractive' DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=5 ' DISTRIBUTION='trixie' HOME='/root' HOST_ARCH='armhf' IFS=' ' INVOCATION_ID='ff16730eda1c4937a187771b97ecff15' 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='25098' 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.HWgTiUnh/pbuilderrc_0ELH --distribution trixie --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/trixie-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.HWgTiUnh/b1 --logfile b1/build.log python-django-registration_3.3-1.dsc' SUDO_GID='114' SUDO_UID='109' SUDO_USER='jenkins' TERM='unknown' TZ='/usr/share/zoneinfo/Etc/GMT+12' USER='root' _='/usr/bin/systemd-run' http_proxy='http://10.0.0.15:3142/' I: uname -a Linux ff64a 6.1.0-21-arm64 #1 SMP Debian 6.1.90-1 (2024-05-03) aarch64 GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 May 6 11:27 /bin -> usr/bin I: user script /srv/workspace/pbuilder/25098/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: armhf 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 ... 19445 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} libdebhelper-perl{a} libelf1t64{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libicu72{a} libjs-jquery{a} libjs-sphinxdoc{a} libjs-underscore{a} libjson-perl{a} libmagic-mgc{a} libmagic1t64{a} libpipeline1{a} libpython3-stdlib{a} libpython3.11-minimal{a} libpython3.11-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libreadline8t64{a} libsub-override-perl{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} po-debconf{a} python-babel-localedata{a} python3{a} python3-alabaster{a} python3-all{a} python3-asgiref{a} python3-babel{a} python3-certifi{a} python3-chardet{a} python3-charset-normalizer{a} python3-confusable-homoglyphs{a} python3-distutils{a} python3-django{a} python3-docutils{a} python3-idna{a} python3-imagesize{a} python3-jinja2{a} python3-lib2to3{a} python3-markupsafe{a} python3-minimal{a} python3-packaging{a} python3-pkg-resources{a} python3-pygments{a} python3-requests{a} python3-roman{a} python3-setuptools{a} python3-six{a} python3-snowballstemmer{a} python3-sphinx{a} python3-sphinx-rtd-theme{a} python3-sphinxcontrib.jquery{a} python3-sqlparse{a} python3-urllib3{a} python3.11{a} python3.11-minimal{a} python3.12{a} python3.12-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 libarchive-cpio-perl libjson-xs-perl libltdl-dev libmail-sendmail-perl libpaper-utils lynx python3-click python3-pil python3-tz wget 0 packages upgraded, 91 newly installed, 0 to remove and 0 not upgraded. Need to get 48.5 MB of archives. After unpacking 208 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian trixie/main armhf fonts-lato all 2.015-1 [2780 kB] Get: 2 http://deb.debian.org/debian trixie/main armhf libpython3.11-minimal armhf 3.11.9-1 [805 kB] Get: 3 http://deb.debian.org/debian trixie/main armhf libexpat1 armhf 2.6.2-1 [83.5 kB] Get: 4 http://deb.debian.org/debian trixie/main armhf python3.11-minimal armhf 3.11.9-1 [1600 kB] Get: 5 http://deb.debian.org/debian trixie/main armhf python3-minimal armhf 3.11.8-1 [26.3 kB] Get: 6 http://deb.debian.org/debian trixie/main armhf media-types all 10.1.0 [26.9 kB] Get: 7 http://deb.debian.org/debian trixie/main armhf netbase all 6.4 [12.8 kB] Get: 8 http://deb.debian.org/debian trixie/main armhf tzdata all 2024a-4 [255 kB] Get: 9 http://deb.debian.org/debian trixie/main armhf readline-common all 8.2-4 [69.3 kB] Get: 10 http://deb.debian.org/debian trixie/main armhf libreadline8t64 armhf 8.2-4 [145 kB] Get: 11 http://deb.debian.org/debian trixie/main armhf libpython3.11-stdlib armhf 3.11.9-1 [1704 kB] Get: 12 http://deb.debian.org/debian trixie/main armhf python3.11 armhf 3.11.9-1 [602 kB] Get: 13 http://deb.debian.org/debian trixie/main armhf libpython3-stdlib armhf 3.11.8-1 [9332 B] Get: 14 http://deb.debian.org/debian trixie/main armhf python3 armhf 3.11.8-1 [27.4 kB] Get: 15 http://deb.debian.org/debian trixie/main armhf libpython3.12-minimal armhf 3.12.3-1 [795 kB] Get: 16 http://deb.debian.org/debian trixie/main armhf python3.12-minimal armhf 3.12.3-1 [1783 kB] Get: 17 http://deb.debian.org/debian trixie/main armhf sgml-base all 1.31 [15.4 kB] Get: 18 http://deb.debian.org/debian trixie/main armhf sensible-utils all 0.0.22 [22.4 kB] Get: 19 http://deb.debian.org/debian trixie/main armhf openssl armhf 3.2.1-3 [1326 kB] Get: 20 http://deb.debian.org/debian trixie/main armhf ca-certificates all 20240203 [158 kB] Get: 21 http://deb.debian.org/debian trixie/main armhf libmagic-mgc armhf 1:5.45-3 [314 kB] Get: 22 http://deb.debian.org/debian trixie/main armhf libmagic1t64 armhf 1:5.45-3 [98.1 kB] Get: 23 http://deb.debian.org/debian trixie/main armhf file armhf 1:5.45-3 [42.0 kB] Get: 24 http://deb.debian.org/debian trixie/main armhf gettext-base armhf 0.21-14+b1 [157 kB] Get: 25 http://deb.debian.org/debian trixie/main armhf libuchardet0 armhf 0.0.8-1+b1 [65.7 kB] Get: 26 http://deb.debian.org/debian trixie/main armhf groff-base armhf 1.23.0-4 [1090 kB] Get: 27 http://deb.debian.org/debian trixie/main armhf bsdextrautils armhf 2.40-8 [85.6 kB] Get: 28 http://deb.debian.org/debian trixie/main armhf libpipeline1 armhf 1.5.7-2 [33.3 kB] Get: 29 http://deb.debian.org/debian trixie/main armhf man-db armhf 2.12.1-1 [1375 kB] Get: 30 http://deb.debian.org/debian trixie/main armhf m4 armhf 1.4.19-4 [264 kB] Get: 31 http://deb.debian.org/debian trixie/main armhf autoconf all 2.71-3 [332 kB] Get: 32 http://deb.debian.org/debian trixie/main armhf autotools-dev all 20220109.1 [51.6 kB] Get: 33 http://deb.debian.org/debian trixie/main armhf automake all 1:1.16.5-1.3 [823 kB] Get: 34 http://deb.debian.org/debian trixie/main armhf autopoint all 0.21-14 [496 kB] Get: 35 http://deb.debian.org/debian trixie/main armhf libdebhelper-perl all 13.15.3 [88.0 kB] Get: 36 http://deb.debian.org/debian trixie/main armhf libtool all 2.4.7-7 [517 kB] Get: 37 http://deb.debian.org/debian trixie/main armhf dh-autoreconf all 20 [17.1 kB] Get: 38 http://deb.debian.org/debian trixie/main armhf libarchive-zip-perl all 1.68-1 [104 kB] Get: 39 http://deb.debian.org/debian trixie/main armhf libsub-override-perl all 0.10-1 [10.6 kB] Get: 40 http://deb.debian.org/debian trixie/main armhf libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB] Get: 41 http://deb.debian.org/debian trixie/main armhf dh-strip-nondeterminism all 1.13.1-1 [8620 B] Get: 42 http://deb.debian.org/debian trixie/main armhf libelf1t64 armhf 0.191-1+b1 [183 kB] Get: 43 http://deb.debian.org/debian trixie/main armhf dwz armhf 0.15-1+b2 [106 kB] Get: 44 http://deb.debian.org/debian trixie/main armhf libicu72 armhf 72.1-4+b1 [9070 kB] Get: 45 http://deb.debian.org/debian trixie/main armhf libxml2 armhf 2.9.14+dfsg-1.3+b3 [598 kB] Get: 46 http://deb.debian.org/debian trixie/main armhf gettext armhf 0.21-14+b1 [1230 kB] Get: 47 http://deb.debian.org/debian trixie/main armhf intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 48 http://deb.debian.org/debian trixie/main armhf po-debconf all 1.0.21+nmu1 [248 kB] Get: 49 http://deb.debian.org/debian trixie/main armhf debhelper all 13.15.3 [901 kB] Get: 50 http://deb.debian.org/debian trixie/main armhf python3-pkg-resources all 68.1.2-2 [241 kB] Get: 51 http://deb.debian.org/debian trixie/main armhf python3-lib2to3 all 3.12.3-1 [77.6 kB] Get: 52 http://deb.debian.org/debian trixie/main armhf python3-distutils all 3.12.3-1 [131 kB] Get: 53 http://deb.debian.org/debian trixie/main armhf python3-setuptools all 68.1.2-2 [468 kB] Get: 54 http://deb.debian.org/debian trixie/main armhf dh-python all 6.20240422 [107 kB] Get: 55 http://deb.debian.org/debian trixie/main armhf xml-core all 0.19 [20.1 kB] Get: 56 http://deb.debian.org/debian trixie/main armhf docutils-common all 0.20.1+dfsg-3 [128 kB] Get: 57 http://deb.debian.org/debian trixie/main armhf fonts-font-awesome all 5.0.10+really4.7.0~dfsg-4.1 [517 kB] Get: 58 http://deb.debian.org/debian trixie/main armhf libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get: 59 http://deb.debian.org/debian trixie/main armhf libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get: 60 http://deb.debian.org/debian trixie/main armhf libjs-sphinxdoc all 7.2.6-6 [150 kB] Get: 61 http://deb.debian.org/debian trixie/main armhf libjson-perl all 4.10000-1 [87.5 kB] Get: 62 http://deb.debian.org/debian trixie/main armhf libpython3.12-stdlib armhf 3.12.3-1 [1808 kB] Get: 63 http://deb.debian.org/debian trixie/main armhf python-babel-localedata all 2.14.0-1 [5701 kB] Get: 64 http://deb.debian.org/debian trixie/main armhf python3-alabaster all 0.7.12-1 [20.8 kB] Get: 65 http://deb.debian.org/debian trixie/main armhf python3.12 armhf 3.12.3-1 [659 kB] Get: 66 http://deb.debian.org/debian trixie/main armhf python3-all armhf 3.11.8-1 [1056 B] Get: 67 http://deb.debian.org/debian trixie/main armhf python3-asgiref all 3.8.1-1 [28.8 kB] Get: 68 http://deb.debian.org/debian trixie/main armhf python3-babel all 2.14.0-1 [111 kB] Get: 69 http://deb.debian.org/debian trixie/main armhf python3-certifi all 2023.11.17-1 [155 kB] Get: 70 http://deb.debian.org/debian trixie/main armhf python3-chardet all 5.2.0+dfsg-1 [107 kB] Get: 71 http://deb.debian.org/debian trixie/main armhf python3-charset-normalizer all 3.3.2-1 [51.6 kB] Get: 72 http://deb.debian.org/debian trixie/main armhf python3-confusable-homoglyphs all 3.3.1-1 [128 kB] Get: 73 http://deb.debian.org/debian trixie/main armhf python3-sqlparse all 0.4.4-1 [37.6 kB] Get: 74 http://deb.debian.org/debian trixie/main armhf python3-django all 3:4.2.11-1 [2736 kB] Get: 75 http://deb.debian.org/debian trixie/main armhf python3-roman all 3.3-3 [9880 B] Get: 76 http://deb.debian.org/debian trixie/main armhf python3-docutils all 0.20.1+dfsg-3 [389 kB] Get: 77 http://deb.debian.org/debian trixie/main armhf python3-idna all 3.6-2 [37.0 kB] Get: 78 http://deb.debian.org/debian trixie/main armhf python3-imagesize all 1.4.1-1 [6688 B] Get: 79 http://deb.debian.org/debian trixie/main armhf python3-markupsafe armhf 2.1.5-1 [13.9 kB] Get: 80 http://deb.debian.org/debian trixie/main armhf python3-jinja2 all 3.1.3-1 [119 kB] Get: 81 http://deb.debian.org/debian trixie/main armhf python3-packaging all 24.0-1 [45.5 kB] Get: 82 http://deb.debian.org/debian trixie/main armhf python3-pygments all 2.17.2+dfsg-1 [818 kB] Get: 83 http://deb.debian.org/debian trixie/main armhf python3-six all 1.16.0-6 [16.3 kB] Get: 84 http://deb.debian.org/debian trixie/main armhf python3-urllib3 all 1.26.18-2 [116 kB] Get: 85 http://deb.debian.org/debian trixie/main armhf python3-requests all 2.31.0+dfsg-1 [68.6 kB] Get: 86 http://deb.debian.org/debian trixie/main armhf python3-snowballstemmer all 2.2.0-4 [58.0 kB] Get: 87 http://deb.debian.org/debian trixie/main armhf sphinx-common all 7.2.6-6 [702 kB] Get: 88 http://deb.debian.org/debian trixie/main armhf python3-sphinx all 7.2.6-6 [552 kB] Get: 89 http://deb.debian.org/debian trixie/main armhf sphinx-rtd-theme-common all 2.0.0+dfsg-1 [1021 kB] Get: 90 http://deb.debian.org/debian trixie/main armhf python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 91 http://deb.debian.org/debian trixie/main armhf python3-sphinx-rtd-theme all 2.0.0+dfsg-1 [28.3 kB] Fetched 48.5 MB in 1s (35.7 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 ... 19445 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.11-minimal:armhf. Preparing to unpack .../libpython3.11-minimal_3.11.9-1_armhf.deb ... Unpacking libpython3.11-minimal:armhf (3.11.9-1) ... Selecting previously unselected package libexpat1:armhf. Preparing to unpack .../libexpat1_2.6.2-1_armhf.deb ... Unpacking libexpat1:armhf (2.6.2-1) ... Selecting previously unselected package python3.11-minimal. Preparing to unpack .../python3.11-minimal_3.11.9-1_armhf.deb ... Unpacking python3.11-minimal (3.11.9-1) ... Setting up libpython3.11-minimal:armhf (3.11.9-1) ... Setting up libexpat1:armhf (2.6.2-1) ... Setting up python3.11-minimal (3.11.9-1) ... Selecting previously unselected package python3-minimal. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 19787 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.11.8-1_armhf.deb ... Unpacking python3-minimal (3.11.8-1) ... Selecting previously unselected package media-types. Preparing to unpack .../1-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../2-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package tzdata. Preparing to unpack .../3-tzdata_2024a-4_all.deb ... Unpacking tzdata (2024a-4) ... Selecting previously unselected package readline-common. Preparing to unpack .../4-readline-common_8.2-4_all.deb ... Unpacking readline-common (8.2-4) ... Selecting previously unselected package libreadline8t64:armhf. Preparing to unpack .../5-libreadline8t64_8.2-4_armhf.deb ... Adding 'diversion of /lib/arm-linux-gnueabihf/libhistory.so.8 to /lib/arm-linux-gnueabihf/libhistory.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/arm-linux-gnueabihf/libhistory.so.8.2 to /lib/arm-linux-gnueabihf/libhistory.so.8.2.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/arm-linux-gnueabihf/libreadline.so.8 to /lib/arm-linux-gnueabihf/libreadline.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/arm-linux-gnueabihf/libreadline.so.8.2 to /lib/arm-linux-gnueabihf/libreadline.so.8.2.usr-is-merged by libreadline8t64' Unpacking libreadline8t64:armhf (8.2-4) ... Selecting previously unselected package libpython3.11-stdlib:armhf. Preparing to unpack .../6-libpython3.11-stdlib_3.11.9-1_armhf.deb ... Unpacking libpython3.11-stdlib:armhf (3.11.9-1) ... Selecting previously unselected package python3.11. Preparing to unpack .../7-python3.11_3.11.9-1_armhf.deb ... Unpacking python3.11 (3.11.9-1) ... Selecting previously unselected package libpython3-stdlib:armhf. Preparing to unpack .../8-libpython3-stdlib_3.11.8-1_armhf.deb ... Unpacking libpython3-stdlib:armhf (3.11.8-1) ... Setting up python3-minimal (3.11.8-1) ... Selecting previously unselected package python3. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 20779 files and directories currently installed.) Preparing to unpack .../00-python3_3.11.8-1_armhf.deb ... Unpacking python3 (3.11.8-1) ... Selecting previously unselected package libpython3.12-minimal:armhf. Preparing to unpack .../01-libpython3.12-minimal_3.12.3-1_armhf.deb ... Unpacking libpython3.12-minimal:armhf (3.12.3-1) ... Selecting previously unselected package python3.12-minimal. Preparing to unpack .../02-python3.12-minimal_3.12.3-1_armhf.deb ... Unpacking python3.12-minimal (3.12.3-1) ... Selecting previously unselected package sgml-base. Preparing to unpack .../03-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../04-sensible-utils_0.0.22_all.deb ... Unpacking sensible-utils (0.0.22) ... Selecting previously unselected package openssl. Preparing to unpack .../05-openssl_3.2.1-3_armhf.deb ... Unpacking openssl (3.2.1-3) ... 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_armhf.deb ... Unpacking libmagic-mgc (1:5.45-3) ... Selecting previously unselected package libmagic1t64:armhf. Preparing to unpack .../08-libmagic1t64_1%3a5.45-3_armhf.deb ... Unpacking libmagic1t64:armhf (1:5.45-3) ... Selecting previously unselected package file. Preparing to unpack .../09-file_1%3a5.45-3_armhf.deb ... Unpacking file (1:5.45-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../10-gettext-base_0.21-14+b1_armhf.deb ... Unpacking gettext-base (0.21-14+b1) ... Selecting previously unselected package libuchardet0:armhf. Preparing to unpack .../11-libuchardet0_0.0.8-1+b1_armhf.deb ... Unpacking libuchardet0:armhf (0.0.8-1+b1) ... Selecting previously unselected package groff-base. Preparing to unpack .../12-groff-base_1.23.0-4_armhf.deb ... Unpacking groff-base (1.23.0-4) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../13-bsdextrautils_2.40-8_armhf.deb ... Unpacking bsdextrautils (2.40-8) ... Selecting previously unselected package libpipeline1:armhf. Preparing to unpack .../14-libpipeline1_1.5.7-2_armhf.deb ... Unpacking libpipeline1:armhf (1.5.7-2) ... Selecting previously unselected package man-db. Preparing to unpack .../15-man-db_2.12.1-1_armhf.deb ... Unpacking man-db (2.12.1-1) ... Selecting previously unselected package m4. Preparing to unpack .../16-m4_1.4.19-4_armhf.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../17-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-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.21-14_all.deb ... Unpacking autopoint (0.21-14) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../21-libdebhelper-perl_13.15.3_all.deb ... Unpacking libdebhelper-perl (13.15.3) ... Selecting previously unselected package libtool. Preparing to unpack .../22-libtool_2.4.7-7_all.deb ... Unpacking libtool (2.4.7-7) ... 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 libsub-override-perl. Preparing to unpack .../25-libsub-override-perl_0.10-1_all.deb ... Unpacking libsub-override-perl (0.10-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../26-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../27-dh-strip-nondeterminism_1.13.1-1_all.deb ... Unpacking dh-strip-nondeterminism (1.13.1-1) ... Selecting previously unselected package libelf1t64:armhf. Preparing to unpack .../28-libelf1t64_0.191-1+b1_armhf.deb ... Unpacking libelf1t64:armhf (0.191-1+b1) ... Selecting previously unselected package dwz. Preparing to unpack .../29-dwz_0.15-1+b2_armhf.deb ... Unpacking dwz (0.15-1+b2) ... Selecting previously unselected package libicu72:armhf. Preparing to unpack .../30-libicu72_72.1-4+b1_armhf.deb ... Unpacking libicu72:armhf (72.1-4+b1) ... Selecting previously unselected package libxml2:armhf. Preparing to unpack .../31-libxml2_2.9.14+dfsg-1.3+b3_armhf.deb ... Unpacking libxml2:armhf (2.9.14+dfsg-1.3+b3) ... Selecting previously unselected package gettext. Preparing to unpack .../32-gettext_0.21-14+b1_armhf.deb ... Unpacking gettext (0.21-14+b1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../33-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 .../34-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../35-debhelper_13.15.3_all.deb ... Unpacking debhelper (13.15.3) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../36-python3-pkg-resources_68.1.2-2_all.deb ... Unpacking python3-pkg-resources (68.1.2-2) ... Selecting previously unselected package python3-lib2to3. Preparing to unpack .../37-python3-lib2to3_3.12.3-1_all.deb ... Unpacking python3-lib2to3 (3.12.3-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../38-python3-distutils_3.12.3-1_all.deb ... Unpacking python3-distutils (3.12.3-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../39-python3-setuptools_68.1.2-2_all.deb ... Unpacking python3-setuptools (68.1.2-2) ... Selecting previously unselected package dh-python. Preparing to unpack .../40-dh-python_6.20240422_all.deb ... Unpacking dh-python (6.20240422) ... Selecting previously unselected package xml-core. Preparing to unpack .../41-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../42-docutils-common_0.20.1+dfsg-3_all.deb ... Unpacking docutils-common (0.20.1+dfsg-3) ... Selecting previously unselected package fonts-font-awesome. Preparing to unpack .../43-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 .../44-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 .../45-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 .../46-libjs-sphinxdoc_7.2.6-6_all.deb ... Unpacking libjs-sphinxdoc (7.2.6-6) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../47-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package libpython3.12-stdlib:armhf. Preparing to unpack .../48-libpython3.12-stdlib_3.12.3-1_armhf.deb ... Unpacking libpython3.12-stdlib:armhf (3.12.3-1) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../49-python-babel-localedata_2.14.0-1_all.deb ... Unpacking python-babel-localedata (2.14.0-1) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../50-python3-alabaster_0.7.12-1_all.deb ... Unpacking python3-alabaster (0.7.12-1) ... Selecting previously unselected package python3.12. Preparing to unpack .../51-python3.12_3.12.3-1_armhf.deb ... Unpacking python3.12 (3.12.3-1) ... Selecting previously unselected package python3-all. Preparing to unpack .../52-python3-all_3.11.8-1_armhf.deb ... Unpacking python3-all (3.11.8-1) ... Selecting previously unselected package python3-asgiref. Preparing to unpack .../53-python3-asgiref_3.8.1-1_all.deb ... Unpacking python3-asgiref (3.8.1-1) ... Selecting previously unselected package python3-babel. Preparing to unpack .../54-python3-babel_2.14.0-1_all.deb ... Unpacking python3-babel (2.14.0-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../55-python3-certifi_2023.11.17-1_all.deb ... Unpacking python3-certifi (2023.11.17-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../56-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 .../57-python3-charset-normalizer_3.3.2-1_all.deb ... Unpacking python3-charset-normalizer (3.3.2-1) ... Selecting previously unselected package python3-confusable-homoglyphs. Preparing to unpack .../58-python3-confusable-homoglyphs_3.3.1-1_all.deb ... Unpacking python3-confusable-homoglyphs (3.3.1-1) ... Selecting previously unselected package python3-sqlparse. Preparing to unpack .../59-python3-sqlparse_0.4.4-1_all.deb ... Unpacking python3-sqlparse (0.4.4-1) ... Selecting previously unselected package python3-django. Preparing to unpack .../60-python3-django_3%3a4.2.11-1_all.deb ... Unpacking python3-django (3:4.2.11-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../61-python3-roman_3.3-3_all.deb ... Unpacking python3-roman (3.3-3) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../62-python3-docutils_0.20.1+dfsg-3_all.deb ... Unpacking python3-docutils (0.20.1+dfsg-3) ... Selecting previously unselected package python3-idna. Preparing to unpack .../63-python3-idna_3.6-2_all.deb ... Unpacking python3-idna (3.6-2) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../64-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../65-python3-markupsafe_2.1.5-1_armhf.deb ... Unpacking python3-markupsafe (2.1.5-1) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../66-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../67-python3-packaging_24.0-1_all.deb ... Unpacking python3-packaging (24.0-1) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../68-python3-pygments_2.17.2+dfsg-1_all.deb ... Unpacking python3-pygments (2.17.2+dfsg-1) ... Selecting previously unselected package python3-six. Preparing to unpack .../69-python3-six_1.16.0-6_all.deb ... Unpacking python3-six (1.16.0-6) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../70-python3-urllib3_1.26.18-2_all.deb ... Unpacking python3-urllib3 (1.26.18-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../71-python3-requests_2.31.0+dfsg-1_all.deb ... Unpacking python3-requests (2.31.0+dfsg-1) ... Selecting previously unselected package python3-snowballstemmer. Preparing to unpack .../72-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../73-sphinx-common_7.2.6-6_all.deb ... Unpacking sphinx-common (7.2.6-6) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../74-python3-sphinx_7.2.6-6_all.deb ... Unpacking python3-sphinx (7.2.6-6) ... Selecting previously unselected package sphinx-rtd-theme-common. Preparing to unpack .../75-sphinx-rtd-theme-common_2.0.0+dfsg-1_all.deb ... Unpacking sphinx-rtd-theme-common (2.0.0+dfsg-1) ... Selecting previously unselected package python3-sphinxcontrib.jquery. Preparing to unpack .../76-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 .../77-python3-sphinx-rtd-theme_2.0.0+dfsg-1_all.deb ... Unpacking python3-sphinx-rtd-theme (2.0.0+dfsg-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:armhf (1.5.7-2) ... Setting up fonts-lato (2.015-1) ... Setting up libicu72:armhf (72.1-4+b1) ... Setting up bsdextrautils (2.40-8) ... Setting up libmagic-mgc (1:5.45-3) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.15.3) ... Setting up libmagic1t64:armhf (1:5.45-3) ... Setting up libpython3.12-minimal:armhf (3.12.3-1) ... Setting up gettext-base (0.21-14+b1) ... Setting up m4 (1.4.19-4) ... Setting up file (1:5.45-3) ... Setting up libelf1t64:armhf (0.191-1+b1) ... Setting up python-babel-localedata (2.14.0-1) ... Setting up tzdata (2024a-4) ... Current default time zone: 'Etc/UTC' Local time is now: Thu May 9 09:27:49 UTC 2024. Universal Time is now: Thu May 9 09:27:49 UTC 2024. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.21-14) ... Setting up autoconf (2.71-3) ... Setting up dwz (0.15-1+b2) ... Setting up sensible-utils (0.0.22) ... Setting up libuchardet0:armhf (0.0.8-1+b1) ... Setting up libjson-perl (4.10000-1) ... Setting up libsub-override-perl (0.10-1) ... Setting up netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up openssl (3.2.1-3) ... Setting up readline-common (8.2-4) ... Setting up libxml2:armhf (2.9.14+dfsg-1.3+b3) ... Setting up fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Setting up sphinx-rtd-theme-common (2.0.0+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.13.1-1) ... Setting up python3.12-minimal (3.12.3-1) ... Setting up gettext (0.21-14+b1) ... Setting up libtool (2.4.7-7) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 146 added, 0 removed; done. Setting up libjs-sphinxdoc (7.2.6-6) ... Setting up libreadline8t64:armhf (8.2-4) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up groff-base (1.23.0-4) ... Setting up xml-core (0.19) ... Setting up libpython3.12-stdlib:armhf (3.12.3-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up libpython3.11-stdlib:armhf (3.11.9-1) ... Setting up python3.12 (3.12.3-1) ... Setting up man-db (2.12.1-1) ... Not building database; man-db/auto-update is not 'true'. Setting up sphinx-common (7.2.6-6) ... Setting up libpython3-stdlib:armhf (3.11.8-1) ... Setting up python3.11 (3.11.9-1) ... Setting up debhelper (13.15.3) ... Setting up python3 (3.11.8-1) ... Setting up python3-markupsafe (2.1.5-1) ... Setting up python3-six (1.16.0-6) ... Setting up python3-roman (3.3-3) ... Setting up python3-jinja2 (3.1.3-1) ... Setting up python3-packaging (24.0-1) ... Setting up python3-sqlparse (0.4.4-1) ... Setting up python3-certifi (2023.11.17-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up python3-idna (3.6-2) ... Setting up python3-urllib3 (1.26.18-2) ... Setting up python3-lib2to3 (3.12.3-1) ... Setting up python3-asgiref (3.8.1-1) ... Setting up python3-imagesize (1.4.1-1) ... Setting up python3-pkg-resources (68.1.2-2) ... Setting up python3-distutils (3.12.3-1) ... python3.12: can't get files for byte-compilation Setting up python3-confusable-homoglyphs (3.3.1-1) ... Setting up python3-django (3:4.2.11-1) ... Setting up python3-setuptools (68.1.2-2) ... Setting up python3-babel (2.14.0-1) ... update-alternatives: using /usr/bin/pybabel-python3 to provide /usr/bin/pybabel (pybabel) in auto mode Setting up python3-charset-normalizer (3.3.2-1) ... Setting up python3-alabaster (0.7.12-1) ... Setting up python3-all (3.11.8-1) ... Setting up python3-pygments (2.17.2+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-requests (2.31.0+dfsg-1) ... Setting up dh-python (6.20240422) ... Processing triggers for libc-bin (2.38-7) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.20.1+dfsg-3) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.20.1+dfsg-3) ... Setting up python3-sphinx (7.2.6-6) ... Setting up python3-sphinxcontrib.jquery (4.1-5) ... Setting up python3-sphinx-rtd-theme (2.0.0+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 armhf 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.12 setup.py clean /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) 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-armv7l' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it I: pybuild base:311: python3.11 setup.py clean /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running clean removing '/build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build' (and everything under it) 'build/bdist.linux-armv7l' does not exist -- can't clean it 'build/scripts-3.11' 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.12 setup.py config /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running config I: pybuild base:311: python3.11 setup.py config /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/zh_CN/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 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/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/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/pt_BR/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.2.6 making output directory... done loading intersphinx inventory from https://docs.djangoproject.com/en/stable/_objects/... loading intersphinx inventory from https://docs.python.org/3/objects.inv... 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 NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')) 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 NewConnectionError(': Failed to establish a new connection: [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 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, 2 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.12 setup.py build /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) 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/exceptions.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/forms.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 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/views.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/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/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/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 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 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/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 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 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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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 creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/locale/ar 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 I: pybuild base:311: /usr/bin/python3 setup.py build /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running build running build_py creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration copying src/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration copying src/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration copying src/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration copying src/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration copying src/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration copying src/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends copying src/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/migrations copying src/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_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.11_django-registration/build/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_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.11_django-registration/build/django_registration/backends/one_step 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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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.11_django-registration/build/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/en/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/es_AR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/tr_TR/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_django-registration/build/django_registration/locale/zh_CN/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_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.11_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.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 98.386s 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.11_django-registration/build; cd /build/reproducible-path/python-django-registration-3.3; PYTHONPATH=/build/reproducible-path/python-django-registration-3.3/src python3.11 /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 98.369s 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.12 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) 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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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-311.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-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-311.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__/forms.cpython-311.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__/signals.cpython-311.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__/validators.cpython-311.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__/views.cpython-311.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__ 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-311.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-312.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/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-311.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-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-311.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__ 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-311.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-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-311.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__/views.cpython-311.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__ 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-311.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-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-311.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__/views.cpython-311.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__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.12 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__/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-311.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__/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__/forms.cpython-311.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-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-311.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-311.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-311.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-311.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/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/validators.py -> /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/backends 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__/urls.cpython-311.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-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-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-311.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-311.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/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/__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/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/__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__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.12_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-311.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/__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/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__/urls.cpython-311.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-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-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-311.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-311.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/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/__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/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/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/__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/signals.py -> /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/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__/0001_initial.cpython-311.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/__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__/__init__.cpython-311.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/__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/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 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/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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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.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 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 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/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.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 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 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.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 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 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.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 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 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/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.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 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 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.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 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 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.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 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/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/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/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/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/__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/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/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/__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/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/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/__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/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/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/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/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 I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) 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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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:204: _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.11_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/exceptions.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/forms.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/signals.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/validators.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/__pycache__ copying src/django_registration/__pycache__/views.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/__pycache__ copying src/django_registration/backends/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/0001_initial.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/migrations/__pycache__ copying src/django_registration/migrations/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/migrations/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/urls.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/activation/__pycache__ copying src/django_registration/backends/activation/__pycache__/views.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/activation/__pycache__ creating /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/urls.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/one_step/__pycache__ copying src/django_registration/backends/one_step/__pycache__/views.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11_django-registration/build/django_registration/backends/one_step/__pycache__ running install_lib creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11 creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__pycache__/exceptions.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__pycache__/forms.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__pycache__/signals.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__pycache__/validators.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__pycache__/views.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/exceptions.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/validators.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/__pycache__/urls.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/__pycache__/views.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/urls.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/activation/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/one_step/__pycache__/urls.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/one_step/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/backends/one_step/__pycache__/views.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/backends/one_step copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/forms.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/signals.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/migrations/__pycache__/0001_initial.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/migrations/__pycache__/__init__.cpython-311.pyc -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations/__pycache__ copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/migrations/__init__.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/migrations/0001_initial.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sv creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/sv/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/sv/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/nb creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/nb/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/nb/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/tr_TR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/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.11/dist-packages/django_registration/locale/pt creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/pt/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/pt/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ru creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ru/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ru/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/pl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/pl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pt_BR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/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.11/dist-packages/django_registration/locale/ca creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ca/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ca/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/sl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/sl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ko creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ko/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ko/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/da creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/da/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/da/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/he creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/he/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/he/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/it creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/it/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/it/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/bg creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/bg/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/bg/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ja creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ja/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ja/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/de creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/de/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/de/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/zh_TW creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/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.11/dist-packages/django_registration/locale/el creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/el/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/el/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/is creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/is/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/is/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/sr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/sr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ar creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ar/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/ar/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/zh_CN creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/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.11/dist-packages/django_registration/locale/es creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/es/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/es/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/es_AR creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/es_AR/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/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.11/dist-packages/django_registration/locale/fa creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/fa/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/fa/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/nl creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/nl/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/nl/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/fr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/fr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/fr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/hr creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/hr/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/hr/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/cs creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/cs/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/cs/LC_MESSAGES creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/en creating /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_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.11/dist-packages/django_registration/locale/en/LC_MESSAGES copying /build/reproducible-path/python-django-registration-3.3/.pybuild/cpython3_3.11_django-registration/build/django_registration/views.py -> /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/exceptions.py to exceptions.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/validators.py to validators.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/urls.py to urls.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/activation/views.py to views.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/urls.py to urls.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/backends/one_step/views.py to views.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/forms.py to forms.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/signals.py to signals.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /build/reproducible-path/python-django-registration-3.3/debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/views.py to views.cpython-311.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.11/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/sv/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/tr_TR/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/ru/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_BR/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/sl/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/da/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/it/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/ja/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/zh_TW/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/is/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/ar/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/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/nl/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/hr/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/en/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sv/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/nb/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/tr_TR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pt/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ru/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/pt_BR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ca/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ko/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/da/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/he/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/it/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/bg/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ja/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/de/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/zh_TW/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/el/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/is/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/sr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/ar/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/zh_CN/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/es/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/es_AR/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/fa/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/nl/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/fr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/hr/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/cs/LC_MESSAGES/django.po' removed 'debian/python3-django-registration/usr/lib/python3.11/dist-packages/django_registration/locale/en/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/nb/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/pt/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/pl/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/ca/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/ko/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/he/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/bg/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/de/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/el/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/nl/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/hr/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/en/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/sr/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/zh_CN/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/es_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 'python-django-registration-doc' in '../python-django-registration-doc_3.3-1_all.deb'. dpkg-deb: building package 'python3-django-registration' in '../python3-django-registration_3.3-1_all.deb'. dpkg-genbuildinfo --build=binary -O../python-django-registration_3.3-1_armhf.buildinfo dpkg-genchanges --build=binary -O../python-django-registration_3.3-1_armhf.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/25098 and its subdirectories I: Current time: Wed May 8 21:34:59 -12 2024 I: pbuilder-time-stamp: 1715247299 Thu May 9 09:35:08 UTC 2024 I: 1st build successful. Starting 2nd build on remote node virt32c-armhf-rb.debian.net. Thu May 9 09:35:08 UTC 2024 I: Preparing to do remote build '2' on virt32c-armhf-rb.debian.net. Thu May 9 09:39:52 UTC 2024 I: Deleting $TMPDIR on virt32c-armhf-rb.debian.net. Thu May 9 09:39:54 UTC 2024 I: python-django-registration_3.3-1_armhf.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: 62101fd8f640d738d8bf8657a8d5b9ee5894b6d9 62592 python-django-registration-doc_3.3-1_all.deb 41fe5314ff02f99e8287def3152ee9f0c9a6df23 7130 python-django-registration_3.3-1_armhf.buildinfo 8fa20b15d3ddf2069f405dab9c33e617f4c5a577 26476 python3-django-registration_3.3-1_all.deb Checksums-Sha256: 636aa1ea2c2110ccfb64be2d9fe01a57d3bcc89cf138e4b586b17c40015ecad8 62592 python-django-registration-doc_3.3-1_all.deb 82b20745cf16ab811629f6229fc40011e14ce20f017455a159f5167fe58a06d4 7130 python-django-registration_3.3-1_armhf.buildinfo 3b81a5a9e462f3fa34e093c0f2535db94bccef09e392b0912f61187f7d81a7bd 26476 python3-django-registration_3.3-1_all.deb Files: 26539c76ee06e8bbc2ca7f0735afc279 62592 doc optional python-django-registration-doc_3.3-1_all.deb 6d66f860357a6fd297c7f61cf919db4b 7130 python optional python-django-registration_3.3-1_armhf.buildinfo c3d60ebd409c3aca0612c3eab259f69a 26476 python optional python3-django-registration_3.3-1_all.deb Thu May 9 09:39:56 UTC 2024 I: diffoscope 265 will be used to compare the two builds: Running as unit: rb-diffoscope-armhf_30-3802.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.HWgTiUnh/python-django-registration_3.3-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.HWgTiUnh/python-django-registration_3.3-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.HWgTiUnh/python-django-registration_3.3-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.HWgTiUnh/b1/python-django-registration_3.3-1_armhf.changes /srv/reproducible-results/rbuild-debian/r-b-build.HWgTiUnh/b2/python-django-registration_3.3-1_armhf.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.380s) 0.380s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.017s) 0.017s 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: 748ms CPU time consumed: 741ms Thu May 9 09:39:57 UTC 2024 I: diffoscope 265 found no differences in the changes files, and a .buildinfo file also exists. Thu May 9 09:39:57 UTC 2024 I: python-django-registration from trixie built successfully and reproducibly on armhf. Thu May 9 09:39:58 UTC 2024 I: Submitting .buildinfo files to external archives: Thu May 9 09:39:58 UTC 2024 I: Submitting 8.0K b1/python-django-registration_3.3-1_armhf.buildinfo.asc Thu May 9 09:39:59 UTC 2024 I: Submitting 8.0K b2/python-django-registration_3.3-1_armhf.buildinfo.asc Thu May 9 09:40:00 UTC 2024 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Thu May 9 09:40:00 UTC 2024 I: Done submitting .buildinfo files. Thu May 9 09:40:00 UTC 2024 I: Removing signed python-django-registration_3.3-1_armhf.buildinfo.asc files: removed './b1/python-django-registration_3.3-1_armhf.buildinfo.asc' removed './b2/python-django-registration_3.3-1_armhf.buildinfo.asc'