Fri May 10 22:16:53 UTC 2024 I: starting to build django-tables/trixie/armhf on jenkins on '2024-05-10 22:16' Fri May 10 22:16:53 UTC 2024 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/armhf_9/5330/console.log Fri May 10 22:16:53 UTC 2024 I: Downloading source for trixie/django-tables=2.7.0-2 --2024-05-10 22:16:53-- http://deb.debian.org/debian/pool/main/d/django-tables/django-tables_2.7.0-2.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2835 (2.8K) [text/prs.lines.tag] Saving to: ‘django-tables_2.7.0-2.dsc’ 0K .. 100% 273M=0s 2024-05-10 22:16:53 (273 MB/s) - ‘django-tables_2.7.0-2.dsc’ saved [2835/2835] Fri May 10 22:16:53 UTC 2024 I: django-tables_2.7.0-2.dsc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: django-tables Binary: python-django-tables2-doc, python3-django-tables2 Architecture: all Version: 2.7.0-2 Maintainer: Debian Python Team Uploaders: Brian May , Homepage: https://github.com/jieter/django-tables2 Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/python-team/packages/django-tables Vcs-Git: https://salsa.debian.org/python-team/packages/django-tables.git Testsuite: autopkgtest Testsuite-Triggers: python3-django, python3-django-filters, python3-fudge, python3-lxml, python3-psycopg2, python3-recommonmark, python3-tablib, python3-tz Build-Depends: debhelper-compat (= 13), dh-sequence-python3, dh-sequence-sphinxdoc, python3-all, python3-setuptools Build-Depends-Indep: python-django-doc , python3-django , python3-django-filters , python3-doc , python3-fudge , python3-lxml , python3-myst-parser , python3-psycopg2 , python3-recommonmark , python3-sphinx , python3-sphinx-rtd-theme , python3-sphinxcontrib.jquery , python3-sphinxcontrib.spelling , python3-tablib , python3-tz Package-List: python-django-tables2-doc deb doc optional arch=all python3-django-tables2 deb python optional arch=all Checksums-Sha1: 696b58c78c655c25c3ebe882870ad9ea2b8878b8 431811 django-tables_2.7.0.orig.tar.gz a5e0faaa2d62f259778221c67aa5aa1e2184dc94 10228 django-tables_2.7.0-2.debian.tar.xz Checksums-Sha256: 7698643bf943333f9339b8e0e8d23fe860785105885820c480edc3daae35ab08 431811 django-tables_2.7.0.orig.tar.gz 1079f2727ee2da397f9b2ef777ae8dcbbf0a6d923fdaefcda5927d60832977a5 10228 django-tables_2.7.0-2.debian.tar.xz Files: ae34b91632adb03179358aeeb7b23916 431811 django-tables_2.7.0.orig.tar.gz 8f5d95e5acdfe1c3068260466513bb4f 10228 django-tables_2.7.0-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmXfgjERHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBraPxAAq8OP7QOVGsXMSQCIbxN2SPgN2tAO3GJU eU1TBxvJuOyU1gd69wmoLAU8VcSTKUP7th0m0nJ1ybNFD9DDhRj1w6wBuXpRFo7x cklmfbKY0SVQLHhZ/m3ypNEpoZs3MOQcgfQY9J+KdgFOryc9zUPO7A65TOpFfdhI EsbONh/4XCkwsBvryo3D21mAQ+J+xevwPh5rNa3GxFx/waXCUv7/7guWE4GSMccV GR80wnaYojXRR53WvpVKq52BOzrH7Ex/lDuNED0YHLNns9u8dTs98n/6zRGN6blq HMtmEv0oAzGBSu98ONuQDTBeLlPdjDgtTlJGgbIIkgT/cHX3LlOt0Oekoccm00qn hgaNTSblBPH/Q7m5d8kTWSdhxBjIydyKcgEIcBLtKQoMXVitClFS3l6XW4upA1F5 2H5um2aIa0tZwZjLrBJ6lwbkBTiQSuU3d7x2Hf93TSoBwLmlGr6XAR9dw36Vv3P+ UQ9rggRDlcMmZyE1rVVNS3DdDoBk9bWG4H35XkH3YKF3djU8n8mtwOn1NzcbhPV7 uwUXgnScBwrKwQ2hr8NujsZ/Hal/+ymBh+Y8DMaz7tmSO2hkdoRo6Ky6JVUPJn4Z EFlQQS657M364qcJExwNXyUIgzOcvvlF7YNX8hIkO5VYU8NltXAH/hYuzqRRwtBa iW3tBIAlWKs= =dSxy -----END PGP SIGNATURE----- Fri May 10 22:16:53 UTC 2024 I: Checking whether the package is not for us Fri May 10 22:16:53 UTC 2024 I: Starting 1st build on remote node virt32a-armhf-rb.debian.net. Fri May 10 22:16:53 UTC 2024 I: Preparing to do remote build '1' on virt32a-armhf-rb.debian.net. Fri May 10 22:26:10 UTC 2024 I: Deleting $TMPDIR on virt32a-armhf-rb.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Fri May 10 10:16:59 -12 2024 I: pbuilder-time-stamp: 1715379419 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 [django-tables_2.7.0-2.dsc] I: copying [./django-tables_2.7.0.orig.tar.gz] I: copying [./django-tables_2.7.0-2.debian.tar.xz] I: Extracting source gpgv: Signature made Wed Feb 28 18:57:53 2024 gpgv: using RSA key 8F6DE104377F3B11E741748731F3144544A1741A gpgv: issuer "tchet@debian.org" gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./django-tables_2.7.0-2.dsc: no acceptable signature found dpkg-source: info: extracting django-tables in django-tables-2.7.0 dpkg-source: info: unpacking django-tables_2.7.0.orig.tar.gz dpkg-source: info: unpacking django-tables_2.7.0-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying debian-hacks/Use-local-copies-of-object.inv-for-building-documentation.patch dpkg-source: info: applying privacy/Replace-privacy-breach-links-by-packaged-copies.patch dpkg-source: info: applying debian-hacks/Remove-test_should_be_used_for_nullbooleanfield.patch dpkg-source: info: applying debian-hacks/Ignore-test_export.ExportViewTest-for-now.patch I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/1017/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=3 ' DISTRIBUTION='trixie' HOME='/root' HOST_ARCH='armhf' IFS=' ' INVOCATION_ID='2934613e8438472390e69c0b7252f48a' 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='1017' 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.1R9xE7xx/pbuilderrc_Vr33 --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.1R9xE7xx/b1 --logfile b1/build.log django-tables_2.7.0-2.dsc' SUDO_GID='113' SUDO_UID='107' 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 virt32a 6.1.0-21-armmp-lpae #1 SMP Debian 6.1.90-1 (2024-05-03) armv7l GNU/Linux I: ls -l /bin lrwxrwxrwx 1 root root 7 May 10 11:24 /bin -> usr/bin I: user script /srv/workspace/pbuilder/1017/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-sequence-python3, dh-sequence-sphinxdoc, python3-all, python3-setuptools, python-django-doc, python3-django, python3-django-filters, python3-doc, python3-fudge, python3-lxml, python3-myst-parser, python3-psycopg2, python3-recommonmark, python3-sphinx, python3-sphinx-rtd-theme, python3-sphinxcontrib.jquery, python3-sphinxcontrib.spelling, python3-tablib, python3-tz 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-sequence-python3; however: Package dh-sequence-python3 is not installed. pbuilder-satisfydepends-dummy depends on dh-sequence-sphinxdoc; however: Package dh-sequence-sphinxdoc 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 python-django-doc; however: Package python-django-doc is not installed. pbuilder-satisfydepends-dummy depends on python3-django; however: Package python3-django is not installed. pbuilder-satisfydepends-dummy depends on python3-django-filters; however: Package python3-django-filters is not installed. pbuilder-satisfydepends-dummy depends on python3-doc; however: Package python3-doc is not installed. pbuilder-satisfydepends-dummy depends on python3-fudge; however: Package python3-fudge is not installed. pbuilder-satisfydepends-dummy depends on python3-lxml; however: Package python3-lxml is not installed. pbuilder-satisfydepends-dummy depends on python3-myst-parser; however: Package python3-myst-parser is not installed. pbuilder-satisfydepends-dummy depends on python3-psycopg2; however: Package python3-psycopg2 is not installed. pbuilder-satisfydepends-dummy depends on python3-recommonmark; however: Package python3-recommonmark 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. pbuilder-satisfydepends-dummy depends on python3-sphinxcontrib.jquery; however: Package python3-sphinxcontrib.jquery is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinxcontrib.spelling; however: Package python3-sphinxcontrib.spelling is not installed. pbuilder-satisfydepends-dummy depends on python3-tablib; however: Package python3-tablib is not installed. pbuilder-satisfydepends-dummy depends on python3-tz; however: Package python3-tz 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} dictionaries-common{a} docutils-common{a} dwz{a} emacsen-common{a} file{a} fonts-font-awesome{a} fonts-lato{a} gettext{a} gettext-base{a} groff-base{a} hunspell-en-us{a} intltool-debian{a} libarchive-zip-perl{a} libaspell15{a} libblas3{a} libcom-err2{a} libdebhelper-perl{a} libelf1t64{a} libenchant-2-2{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libgfortran5{a} libglib2.0-0t64{a} libgssapi-krb5-2{a} libhunspell-1.7-0{a} libicu72{a} libjs-jquery{a} libjs-sphinxdoc{a} libjs-underscore{a} libjson-perl{a} libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} liblapack3{a} libldap-2.5-0{a} libmagic-mgc{a} libmagic1t64{a} libpipeline1{a} libpq5{a} libpython3-stdlib{a} libpython3.11-minimal{a} libpython3.11-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libreadline8t64{a} libsasl2-2{a} libsasl2-modules-db{a} libsub-override-perl{a} libtext-iconv-perl{a} libtool{a} libuchardet0{a} libxml2{a} libxslt1.1{a} libyaml-0-2{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} po-debconf{a} python-babel-localedata{a} python-django-doc{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-commonmark{a} python3-dateutil{a} python3-defusedxml{a} python3-distutils{a} python3-django{a} python3-django-filters{a} python3-doc{a} python3-docutils{a} python3-enchant{a} python3-et-xmlfile{a} python3-fudge{a} python3-idna{a} python3-imagesize{a} python3-importlib-metadata{a} python3-jinja2{a} python3-lib2to3{a} python3-lxml{a} python3-markdown-it{a} python3-markupsafe{a} python3-mdit-py-plugins{a} python3-mdurl{a} python3-minimal{a} python3-more-itertools{a} python3-myst-parser{a} python3-numpy{a} python3-odf{a} python3-openpyxl{a} python3-packaging{a} python3-pandas{a} python3-pandas-lib{a} python3-pkg-resources{a} python3-psycopg2{a} python3-pygments{a} python3-recommonmark{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-sphinxcontrib.spelling{a} python3-sqlparse{a} python3-tablib{a} python3-tabulate{a} python3-tz{a} python3-urllib3{a} python3-xlrd{a} python3-xlwt{a} python3-yaml{a} python3-zipp{a} python3.11{a} python3.11-doc{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: aspell-am aspell-ar aspell-ar-large aspell-bg aspell-br aspell-ca aspell-cs aspell-cy aspell-da aspell-de aspell-de-1901 aspell-el aspell-en aspell-eo aspell-eo-cx7 aspell-es aspell-et aspell-eu aspell-fa aspell-fo aspell-fr aspell-ga aspell-gl-minimos aspell-he aspell-hr aspell-hsb aspell-hu aspell-hy aspell-is aspell-it aspell-kk aspell-ku aspell-lt aspell-lv aspell-nl aspell-no aspell-pl aspell-pt-br aspell-pt-pt aspell-ro aspell-ru aspell-sk aspell-sl aspell-sv aspell-tl aspell-uk aspell-uz curl enchant-2 javascript-common krb5-locales libarchive-cpio-perl libglib2.0-data libjson-xs-perl libldap-common libltdl-dev libmail-sendmail-perl libpaper-utils libsasl2-modules lynx python-fudge-doc python-odf-doc python-odf-tools python3-bottleneck python3-bs4 python3-cssselect python3-html5lib python3-matplotlib python3-numexpr python3-pil python3-scipy python3-tables shared-mime-info wget xdg-user-dirs 0 packages upgraded, 145 newly installed, 0 to remove and 0 not upgraded. Need to get 87.8 MB of archives. After unpacking 410 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 libtext-iconv-perl armhf 1.7-8+b3 [13.7 kB] Get: 56 http://deb.debian.org/debian trixie/main armhf emacsen-common all 3.0.5 [12.3 kB] Get: 57 http://deb.debian.org/debian trixie/main armhf dictionaries-common all 1.29.7 [184 kB] Get: 58 http://deb.debian.org/debian trixie/main armhf xml-core all 0.19 [20.1 kB] Get: 59 http://deb.debian.org/debian trixie/main armhf docutils-common all 0.20.1+dfsg-3 [128 kB] Get: 60 http://deb.debian.org/debian trixie/main armhf fonts-font-awesome all 5.0.10+really4.7.0~dfsg-4.1 [517 kB] Get: 61 http://deb.debian.org/debian trixie/main armhf hunspell-en-us all 1:2020.12.07-2 [269 kB] Get: 62 http://deb.debian.org/debian trixie/main armhf libaspell15 armhf 0.60.8.1-1+b1 [292 kB] Get: 63 http://deb.debian.org/debian trixie/main armhf libblas3 armhf 3.12.0-3 [108 kB] Get: 64 http://deb.debian.org/debian trixie/main armhf libcom-err2 armhf 1.47.1~rc2-1 [21.8 kB] Get: 65 http://deb.debian.org/debian trixie/main armhf libglib2.0-0t64 armhf 2.80.1-1 [1314 kB] Get: 66 http://deb.debian.org/debian trixie/main armhf libhunspell-1.7-0 armhf 1.7.2+really1.7.2-10+b2 [216 kB] Get: 67 http://deb.debian.org/debian trixie/main armhf libenchant-2-2 armhf 2.3.3-2+b2 [40.3 kB] Get: 68 http://deb.debian.org/debian trixie/main armhf libgfortran5 armhf 14-20240330-1 [264 kB] Get: 69 http://deb.debian.org/debian trixie/main armhf libkrb5support0 armhf 1.20.1-6+b1 [30.6 kB] Get: 70 http://deb.debian.org/debian trixie/main armhf libk5crypto3 armhf 1.20.1-6+b1 [75.5 kB] Get: 71 http://deb.debian.org/debian trixie/main armhf libkeyutils1 armhf 1.6.3-3 [7908 B] Get: 72 http://deb.debian.org/debian trixie/main armhf libkrb5-3 armhf 1.20.1-6+b1 [290 kB] Get: 73 http://deb.debian.org/debian trixie/main armhf libgssapi-krb5-2 armhf 1.20.1-6+b1 [112 kB] Get: 74 http://deb.debian.org/debian trixie/main armhf libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get: 75 http://deb.debian.org/debian trixie/main armhf libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get: 76 http://deb.debian.org/debian trixie/main armhf libjs-sphinxdoc all 7.2.6-6 [150 kB] Get: 77 http://deb.debian.org/debian trixie/main armhf libjson-perl all 4.10000-1 [87.5 kB] Get: 78 http://deb.debian.org/debian trixie/main armhf liblapack3 armhf 3.12.0-3 [1803 kB] Get: 79 http://deb.debian.org/debian trixie/main armhf libsasl2-modules-db armhf 2.1.28+dfsg1-6 [18.0 kB] Get: 80 http://deb.debian.org/debian trixie/main armhf libsasl2-2 armhf 2.1.28+dfsg1-6 [50.1 kB] Get: 81 http://deb.debian.org/debian trixie/main armhf libldap-2.5-0 armhf 2.5.17+dfsg-1 [161 kB] Get: 82 http://deb.debian.org/debian trixie/main armhf libpq5 armhf 16.2-2+b1 [198 kB] Get: 83 http://deb.debian.org/debian trixie/main armhf libpython3.12-stdlib armhf 3.12.3-1 [1808 kB] Get: 84 http://deb.debian.org/debian trixie/main armhf libxslt1.1 armhf 1.1.35-1+b1 [212 kB] Get: 85 http://deb.debian.org/debian trixie/main armhf libyaml-0-2 armhf 0.2.5-1+b1 [45.5 kB] Get: 86 http://deb.debian.org/debian trixie/main armhf python-babel-localedata all 2.14.0-1 [5701 kB] Get: 87 http://deb.debian.org/debian trixie/main armhf python-django-doc all 3:4.2.11-1 [3588 kB] Get: 88 http://deb.debian.org/debian trixie/main armhf python3-alabaster all 0.7.12-1 [20.8 kB] Get: 89 http://deb.debian.org/debian trixie/main armhf python3.12 armhf 3.12.3-1 [659 kB] Get: 90 http://deb.debian.org/debian trixie/main armhf python3-all armhf 3.11.8-1 [1056 B] Get: 91 http://deb.debian.org/debian trixie/main armhf python3-asgiref all 3.8.1-1 [28.8 kB] Get: 92 http://deb.debian.org/debian trixie/main armhf python3-tz all 2024.1-2 [30.9 kB] Get: 93 http://deb.debian.org/debian trixie/main armhf python3-babel all 2.14.0-1 [111 kB] Get: 94 http://deb.debian.org/debian trixie/main armhf python3-certifi all 2023.11.17-1 [155 kB] Get: 95 http://deb.debian.org/debian trixie/main armhf python3-chardet all 5.2.0+dfsg-1 [107 kB] Get: 96 http://deb.debian.org/debian trixie/main armhf python3-charset-normalizer all 3.3.2-1 [51.6 kB] Get: 97 http://deb.debian.org/debian trixie/main armhf python3-commonmark all 0.9.1-6 [45.3 kB] Get: 98 http://deb.debian.org/debian trixie/main armhf python3-six all 1.16.0-6 [16.3 kB] Get: 99 http://deb.debian.org/debian trixie/main armhf python3-dateutil all 2.9.0-2 [79.4 kB] Get: 100 http://deb.debian.org/debian trixie/main armhf python3-defusedxml all 0.7.1-2 [43.3 kB] Get: 101 http://deb.debian.org/debian trixie/main armhf python3-sqlparse all 0.4.4-1 [37.6 kB] Get: 102 http://deb.debian.org/debian trixie/main armhf python3-django all 3:4.2.11-1 [2736 kB] Get: 103 http://deb.debian.org/debian trixie/main armhf python3-django-filters all 24.2-1 [51.8 kB] Get: 104 http://deb.debian.org/debian trixie/main armhf python3.11-doc all 3.11.9-1 [12.6 MB] Get: 105 http://deb.debian.org/debian trixie/main armhf python3-doc all 3.11.8-1 [9528 B] Get: 106 http://deb.debian.org/debian trixie/main armhf python3-roman all 3.3-3 [9880 B] Get: 107 http://deb.debian.org/debian trixie/main armhf python3-docutils all 0.20.1+dfsg-3 [389 kB] Get: 108 http://deb.debian.org/debian trixie/main armhf python3-enchant all 3.2.2-1 [39.2 kB] Get: 109 http://deb.debian.org/debian trixie/main armhf python3-et-xmlfile all 1.0.1-2.1 [9180 B] Get: 110 http://deb.debian.org/debian trixie/main armhf python3-fudge all 1.1.1-2 [30.2 kB] Get: 111 http://deb.debian.org/debian trixie/main armhf python3-idna all 3.6-2 [37.0 kB] Get: 112 http://deb.debian.org/debian trixie/main armhf python3-imagesize all 1.4.1-1 [6688 B] Get: 113 http://deb.debian.org/debian trixie/main armhf python3-more-itertools all 10.2.0-1 [59.9 kB] Get: 114 http://deb.debian.org/debian trixie/main armhf python3-zipp all 1.0.0-6 [6696 B] Get: 115 http://deb.debian.org/debian trixie/main armhf python3-importlib-metadata all 4.12.0-1 [24.9 kB] Get: 116 http://deb.debian.org/debian trixie/main armhf python3-markupsafe armhf 2.1.5-1 [13.9 kB] Get: 117 http://deb.debian.org/debian trixie/main armhf python3-jinja2 all 3.1.3-1 [119 kB] Get: 118 http://deb.debian.org/debian trixie/main armhf python3-lxml armhf 5.1.0-1 [1878 kB] Get: 119 http://deb.debian.org/debian trixie/main armhf python3-mdurl all 0.1.2-1 [9444 B] Get: 120 http://deb.debian.org/debian trixie/main armhf python3-markdown-it all 3.0.0-2 [62.5 kB] Get: 121 http://deb.debian.org/debian trixie/main armhf python3-mdit-py-plugins all 0.4.0-1 [33.0 kB] Get: 122 http://deb.debian.org/debian trixie/main armhf sphinx-common all 7.2.6-6 [702 kB] Get: 123 http://deb.debian.org/debian trixie/main armhf python3-packaging all 24.0-1 [45.5 kB] Get: 124 http://deb.debian.org/debian trixie/main armhf python3-pygments all 2.17.2+dfsg-1 [818 kB] Get: 125 http://deb.debian.org/debian trixie/main armhf python3-urllib3 all 1.26.18-2 [116 kB] Get: 126 http://deb.debian.org/debian trixie/main armhf python3-requests all 2.31.0+dfsg-1 [68.6 kB] Get: 127 http://deb.debian.org/debian trixie/main armhf python3-snowballstemmer all 2.2.0-4 [58.0 kB] Get: 128 http://deb.debian.org/debian trixie/main armhf python3-sphinx all 7.2.6-6 [552 kB] Get: 129 http://deb.debian.org/debian trixie/main armhf python3-yaml armhf 6.0.1-2 [162 kB] Get: 130 http://deb.debian.org/debian trixie/main armhf python3-myst-parser all 3.0.1-1 [77.5 kB] Get: 131 http://deb.debian.org/debian trixie/main armhf python3-numpy armhf 1:1.26.4+ds-8 [4132 kB] Get: 132 http://deb.debian.org/debian trixie/main armhf python3-odf all 1.4.2-2 [78.0 kB] Get: 133 http://deb.debian.org/debian trixie/main armhf python3-openpyxl all 3.1.2+dfsg-6 [165 kB] Get: 134 http://deb.debian.org/debian trixie/main armhf python3-pandas-lib armhf 2.1.4+dfsg-8 [7001 kB] Get: 135 http://deb.debian.org/debian trixie/main armhf python3-pandas all 2.1.4+dfsg-8 [3015 kB] Get: 136 http://deb.debian.org/debian trixie/main armhf python3-psycopg2 armhf 2.9.9-1+b1 [146 kB] Get: 137 http://deb.debian.org/debian trixie/main armhf python3-recommonmark all 0.7.1+ds-5 [17.3 kB] Get: 138 http://deb.debian.org/debian trixie/main armhf sphinx-rtd-theme-common all 2.0.0+dfsg-1 [1021 kB] Get: 139 http://deb.debian.org/debian trixie/main armhf python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 140 http://deb.debian.org/debian trixie/main armhf python3-sphinx-rtd-theme all 2.0.0+dfsg-1 [28.3 kB] Get: 141 http://deb.debian.org/debian trixie/main armhf python3-sphinxcontrib.spelling all 7.7.0-1 [34.3 kB] Get: 142 http://deb.debian.org/debian trixie/main armhf python3-tabulate all 0.8.10-1 [38.8 kB] Get: 143 http://deb.debian.org/debian trixie/main armhf python3-xlrd all 2.0.1-2 [88.9 kB] Get: 144 http://deb.debian.org/debian trixie/main armhf python3-xlwt all 1.3.0-4 [86.1 kB] Get: 145 http://deb.debian.org/debian trixie/main armhf python3-tablib all 3.6.0-1 [39.9 kB] Fetched 87.8 MB in 13s (6638 kB/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 .../000-python3_3.11.8-1_armhf.deb ... Unpacking python3 (3.11.8-1) ... Selecting previously unselected package libpython3.12-minimal:armhf. Preparing to unpack .../001-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 .../002-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 .../003-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../004-sensible-utils_0.0.22_all.deb ... Unpacking sensible-utils (0.0.22) ... Selecting previously unselected package openssl. Preparing to unpack .../005-openssl_3.2.1-3_armhf.deb ... Unpacking openssl (3.2.1-3) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../006-ca-certificates_20240203_all.deb ... Unpacking ca-certificates (20240203) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../007-libmagic-mgc_1%3a5.45-3_armhf.deb ... Unpacking libmagic-mgc (1:5.45-3) ... Selecting previously unselected package libmagic1t64:armhf. Preparing to unpack .../008-libmagic1t64_1%3a5.45-3_armhf.deb ... Unpacking libmagic1t64:armhf (1:5.45-3) ... Selecting previously unselected package file. Preparing to unpack .../009-file_1%3a5.45-3_armhf.deb ... Unpacking file (1:5.45-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../010-gettext-base_0.21-14+b1_armhf.deb ... Unpacking gettext-base (0.21-14+b1) ... Selecting previously unselected package libuchardet0:armhf. Preparing to unpack .../011-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 .../012-groff-base_1.23.0-4_armhf.deb ... Unpacking groff-base (1.23.0-4) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../013-bsdextrautils_2.40-8_armhf.deb ... Unpacking bsdextrautils (2.40-8) ... Selecting previously unselected package libpipeline1:armhf. Preparing to unpack .../014-libpipeline1_1.5.7-2_armhf.deb ... Unpacking libpipeline1:armhf (1.5.7-2) ... Selecting previously unselected package man-db. Preparing to unpack .../015-man-db_2.12.1-1_armhf.deb ... Unpacking man-db (2.12.1-1) ... Selecting previously unselected package m4. Preparing to unpack .../016-m4_1.4.19-4_armhf.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../017-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../018-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../019-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 .../020-autopoint_0.21-14_all.deb ... Unpacking autopoint (0.21-14) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../021-libdebhelper-perl_13.15.3_all.deb ... Unpacking libdebhelper-perl (13.15.3) ... Selecting previously unselected package libtool. Preparing to unpack .../022-libtool_2.4.7-7_all.deb ... Unpacking libtool (2.4.7-7) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../023-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../024-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 .../025-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 .../026-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 .../027-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 .../028-libelf1t64_0.191-1+b1_armhf.deb ... Unpacking libelf1t64:armhf (0.191-1+b1) ... Selecting previously unselected package dwz. Preparing to unpack .../029-dwz_0.15-1+b2_armhf.deb ... Unpacking dwz (0.15-1+b2) ... Selecting previously unselected package libicu72:armhf. Preparing to unpack .../030-libicu72_72.1-4+b1_armhf.deb ... Unpacking libicu72:armhf (72.1-4+b1) ... Selecting previously unselected package libxml2:armhf. Preparing to unpack .../031-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 .../032-gettext_0.21-14+b1_armhf.deb ... Unpacking gettext (0.21-14+b1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../033-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 .../034-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../035-debhelper_13.15.3_all.deb ... Unpacking debhelper (13.15.3) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../036-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 .../037-python3-lib2to3_3.12.3-1_all.deb ... Unpacking python3-lib2to3 (3.12.3-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../038-python3-distutils_3.12.3-1_all.deb ... Unpacking python3-distutils (3.12.3-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../039-python3-setuptools_68.1.2-2_all.deb ... Unpacking python3-setuptools (68.1.2-2) ... Selecting previously unselected package dh-python. Preparing to unpack .../040-dh-python_6.20240422_all.deb ... Unpacking dh-python (6.20240422) ... Selecting previously unselected package libtext-iconv-perl:armhf. Preparing to unpack .../041-libtext-iconv-perl_1.7-8+b3_armhf.deb ... Unpacking libtext-iconv-perl:armhf (1.7-8+b3) ... Selecting previously unselected package emacsen-common. Preparing to unpack .../042-emacsen-common_3.0.5_all.deb ... Unpacking emacsen-common (3.0.5) ... Selecting previously unselected package dictionaries-common. Preparing to unpack .../043-dictionaries-common_1.29.7_all.deb ... Adding 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Unpacking dictionaries-common (1.29.7) ... Selecting previously unselected package xml-core. Preparing to unpack .../044-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../045-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 .../046-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 hunspell-en-us. Preparing to unpack .../047-hunspell-en-us_1%3a2020.12.07-2_all.deb ... Unpacking hunspell-en-us (1:2020.12.07-2) ... Selecting previously unselected package libaspell15:armhf. Preparing to unpack .../048-libaspell15_0.60.8.1-1+b1_armhf.deb ... Unpacking libaspell15:armhf (0.60.8.1-1+b1) ... Selecting previously unselected package libblas3:armhf. Preparing to unpack .../049-libblas3_3.12.0-3_armhf.deb ... Unpacking libblas3:armhf (3.12.0-3) ... Selecting previously unselected package libcom-err2:armhf. Preparing to unpack .../050-libcom-err2_1.47.1~rc2-1_armhf.deb ... Unpacking libcom-err2:armhf (1.47.1~rc2-1) ... Selecting previously unselected package libglib2.0-0t64:armhf. Preparing to unpack .../051-libglib2.0-0t64_2.80.1-1_armhf.deb ... Unpacking libglib2.0-0t64:armhf (2.80.1-1) ... Selecting previously unselected package libhunspell-1.7-0:armhf. Preparing to unpack .../052-libhunspell-1.7-0_1.7.2+really1.7.2-10+b2_armhf.deb ... Unpacking libhunspell-1.7-0:armhf (1.7.2+really1.7.2-10+b2) ... Selecting previously unselected package libenchant-2-2:armhf. Preparing to unpack .../053-libenchant-2-2_2.3.3-2+b2_armhf.deb ... Unpacking libenchant-2-2:armhf (2.3.3-2+b2) ... Selecting previously unselected package libgfortran5:armhf. Preparing to unpack .../054-libgfortran5_14-20240330-1_armhf.deb ... Unpacking libgfortran5:armhf (14-20240330-1) ... Selecting previously unselected package libkrb5support0:armhf. Preparing to unpack .../055-libkrb5support0_1.20.1-6+b1_armhf.deb ... Unpacking libkrb5support0:armhf (1.20.1-6+b1) ... Selecting previously unselected package libk5crypto3:armhf. Preparing to unpack .../056-libk5crypto3_1.20.1-6+b1_armhf.deb ... Unpacking libk5crypto3:armhf (1.20.1-6+b1) ... Selecting previously unselected package libkeyutils1:armhf. Preparing to unpack .../057-libkeyutils1_1.6.3-3_armhf.deb ... Unpacking libkeyutils1:armhf (1.6.3-3) ... Selecting previously unselected package libkrb5-3:armhf. Preparing to unpack .../058-libkrb5-3_1.20.1-6+b1_armhf.deb ... Unpacking libkrb5-3:armhf (1.20.1-6+b1) ... Selecting previously unselected package libgssapi-krb5-2:armhf. Preparing to unpack .../059-libgssapi-krb5-2_1.20.1-6+b1_armhf.deb ... Unpacking libgssapi-krb5-2:armhf (1.20.1-6+b1) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../060-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 .../061-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 .../062-libjs-sphinxdoc_7.2.6-6_all.deb ... Unpacking libjs-sphinxdoc (7.2.6-6) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../063-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package liblapack3:armhf. Preparing to unpack .../064-liblapack3_3.12.0-3_armhf.deb ... Unpacking liblapack3:armhf (3.12.0-3) ... Selecting previously unselected package libsasl2-modules-db:armhf. Preparing to unpack .../065-libsasl2-modules-db_2.1.28+dfsg1-6_armhf.deb ... Unpacking libsasl2-modules-db:armhf (2.1.28+dfsg1-6) ... Selecting previously unselected package libsasl2-2:armhf. Preparing to unpack .../066-libsasl2-2_2.1.28+dfsg1-6_armhf.deb ... Unpacking libsasl2-2:armhf (2.1.28+dfsg1-6) ... Selecting previously unselected package libldap-2.5-0:armhf. Preparing to unpack .../067-libldap-2.5-0_2.5.17+dfsg-1_armhf.deb ... Unpacking libldap-2.5-0:armhf (2.5.17+dfsg-1) ... Selecting previously unselected package libpq5:armhf. Preparing to unpack .../068-libpq5_16.2-2+b1_armhf.deb ... Unpacking libpq5:armhf (16.2-2+b1) ... Selecting previously unselected package libpython3.12-stdlib:armhf. Preparing to unpack .../069-libpython3.12-stdlib_3.12.3-1_armhf.deb ... Unpacking libpython3.12-stdlib:armhf (3.12.3-1) ... Selecting previously unselected package libxslt1.1:armhf. Preparing to unpack .../070-libxslt1.1_1.1.35-1+b1_armhf.deb ... Unpacking libxslt1.1:armhf (1.1.35-1+b1) ... Selecting previously unselected package libyaml-0-2:armhf. Preparing to unpack .../071-libyaml-0-2_0.2.5-1+b1_armhf.deb ... Unpacking libyaml-0-2:armhf (0.2.5-1+b1) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../072-python-babel-localedata_2.14.0-1_all.deb ... Unpacking python-babel-localedata (2.14.0-1) ... Selecting previously unselected package python-django-doc. Preparing to unpack .../073-python-django-doc_3%3a4.2.11-1_all.deb ... Unpacking python-django-doc (3:4.2.11-1) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../074-python3-alabaster_0.7.12-1_all.deb ... Unpacking python3-alabaster (0.7.12-1) ... Selecting previously unselected package python3.12. Preparing to unpack .../075-python3.12_3.12.3-1_armhf.deb ... Unpacking python3.12 (3.12.3-1) ... Selecting previously unselected package python3-all. Preparing to unpack .../076-python3-all_3.11.8-1_armhf.deb ... Unpacking python3-all (3.11.8-1) ... Selecting previously unselected package python3-asgiref. Preparing to unpack .../077-python3-asgiref_3.8.1-1_all.deb ... Unpacking python3-asgiref (3.8.1-1) ... Selecting previously unselected package python3-tz. Preparing to unpack .../078-python3-tz_2024.1-2_all.deb ... Unpacking python3-tz (2024.1-2) ... Selecting previously unselected package python3-babel. Preparing to unpack .../079-python3-babel_2.14.0-1_all.deb ... Unpacking python3-babel (2.14.0-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../080-python3-certifi_2023.11.17-1_all.deb ... Unpacking python3-certifi (2023.11.17-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../081-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 .../082-python3-charset-normalizer_3.3.2-1_all.deb ... Unpacking python3-charset-normalizer (3.3.2-1) ... Selecting previously unselected package python3-commonmark. Preparing to unpack .../083-python3-commonmark_0.9.1-6_all.deb ... Unpacking python3-commonmark (0.9.1-6) ... Selecting previously unselected package python3-six. Preparing to unpack .../084-python3-six_1.16.0-6_all.deb ... Unpacking python3-six (1.16.0-6) ... Selecting previously unselected package python3-dateutil. Preparing to unpack .../085-python3-dateutil_2.9.0-2_all.deb ... Unpacking python3-dateutil (2.9.0-2) ... Selecting previously unselected package python3-defusedxml. Preparing to unpack .../086-python3-defusedxml_0.7.1-2_all.deb ... Unpacking python3-defusedxml (0.7.1-2) ... Selecting previously unselected package python3-sqlparse. Preparing to unpack .../087-python3-sqlparse_0.4.4-1_all.deb ... Unpacking python3-sqlparse (0.4.4-1) ... Selecting previously unselected package python3-django. Preparing to unpack .../088-python3-django_3%3a4.2.11-1_all.deb ... Unpacking python3-django (3:4.2.11-1) ... Selecting previously unselected package python3-django-filters. Preparing to unpack .../089-python3-django-filters_24.2-1_all.deb ... Unpacking python3-django-filters (24.2-1) ... Selecting previously unselected package python3.11-doc. Preparing to unpack .../090-python3.11-doc_3.11.9-1_all.deb ... Unpacking python3.11-doc (3.11.9-1) ... Selecting previously unselected package python3-doc. Preparing to unpack .../091-python3-doc_3.11.8-1_all.deb ... Unpacking python3-doc (3.11.8-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../092-python3-roman_3.3-3_all.deb ... Unpacking python3-roman (3.3-3) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../093-python3-docutils_0.20.1+dfsg-3_all.deb ... Unpacking python3-docutils (0.20.1+dfsg-3) ... Selecting previously unselected package python3-enchant. Preparing to unpack .../094-python3-enchant_3.2.2-1_all.deb ... Unpacking python3-enchant (3.2.2-1) ... Selecting previously unselected package python3-et-xmlfile. Preparing to unpack .../095-python3-et-xmlfile_1.0.1-2.1_all.deb ... Unpacking python3-et-xmlfile (1.0.1-2.1) ... Selecting previously unselected package python3-fudge. Preparing to unpack .../096-python3-fudge_1.1.1-2_all.deb ... Unpacking python3-fudge (1.1.1-2) ... Selecting previously unselected package python3-idna. Preparing to unpack .../097-python3-idna_3.6-2_all.deb ... Unpacking python3-idna (3.6-2) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../098-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../099-python3-more-itertools_10.2.0-1_all.deb ... Unpacking python3-more-itertools (10.2.0-1) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../100-python3-zipp_1.0.0-6_all.deb ... Unpacking python3-zipp (1.0.0-6) ... Selecting previously unselected package python3-importlib-metadata. Preparing to unpack .../101-python3-importlib-metadata_4.12.0-1_all.deb ... Unpacking python3-importlib-metadata (4.12.0-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../102-python3-markupsafe_2.1.5-1_armhf.deb ... Unpacking python3-markupsafe (2.1.5-1) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../103-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-lxml:armhf. Preparing to unpack .../104-python3-lxml_5.1.0-1_armhf.deb ... Unpacking python3-lxml:armhf (5.1.0-1) ... Selecting previously unselected package python3-mdurl. Preparing to unpack .../105-python3-mdurl_0.1.2-1_all.deb ... Unpacking python3-mdurl (0.1.2-1) ... Selecting previously unselected package python3-markdown-it. Preparing to unpack .../106-python3-markdown-it_3.0.0-2_all.deb ... Unpacking python3-markdown-it (3.0.0-2) ... Selecting previously unselected package python3-mdit-py-plugins. Preparing to unpack .../107-python3-mdit-py-plugins_0.4.0-1_all.deb ... Unpacking python3-mdit-py-plugins (0.4.0-1) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../108-sphinx-common_7.2.6-6_all.deb ... Unpacking sphinx-common (7.2.6-6) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../109-python3-packaging_24.0-1_all.deb ... Unpacking python3-packaging (24.0-1) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../110-python3-pygments_2.17.2+dfsg-1_all.deb ... Unpacking python3-pygments (2.17.2+dfsg-1) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../111-python3-urllib3_1.26.18-2_all.deb ... Unpacking python3-urllib3 (1.26.18-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../112-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 .../113-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../114-python3-sphinx_7.2.6-6_all.deb ... Unpacking python3-sphinx (7.2.6-6) ... Selecting previously unselected package python3-yaml. Preparing to unpack .../115-python3-yaml_6.0.1-2_armhf.deb ... Unpacking python3-yaml (6.0.1-2) ... Selecting previously unselected package python3-myst-parser. Preparing to unpack .../116-python3-myst-parser_3.0.1-1_all.deb ... Unpacking python3-myst-parser (3.0.1-1) ... Selecting previously unselected package python3-numpy. Preparing to unpack .../117-python3-numpy_1%3a1.26.4+ds-8_armhf.deb ... Unpacking python3-numpy (1:1.26.4+ds-8) ... Selecting previously unselected package python3-odf. Preparing to unpack .../118-python3-odf_1.4.2-2_all.deb ... Unpacking python3-odf (1.4.2-2) ... Selecting previously unselected package python3-openpyxl. Preparing to unpack .../119-python3-openpyxl_3.1.2+dfsg-6_all.deb ... Unpacking python3-openpyxl (3.1.2+dfsg-6) ... Selecting previously unselected package python3-pandas-lib:armhf. Preparing to unpack .../120-python3-pandas-lib_2.1.4+dfsg-8_armhf.deb ... Unpacking python3-pandas-lib:armhf (2.1.4+dfsg-8) ... Selecting previously unselected package python3-pandas. Preparing to unpack .../121-python3-pandas_2.1.4+dfsg-8_all.deb ... Unpacking python3-pandas (2.1.4+dfsg-8) ... Selecting previously unselected package python3-psycopg2. Preparing to unpack .../122-python3-psycopg2_2.9.9-1+b1_armhf.deb ... Unpacking python3-psycopg2 (2.9.9-1+b1) ... Selecting previously unselected package python3-recommonmark. Preparing to unpack .../123-python3-recommonmark_0.7.1+ds-5_all.deb ... Unpacking python3-recommonmark (0.7.1+ds-5) ... Selecting previously unselected package sphinx-rtd-theme-common. Preparing to unpack .../124-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 .../125-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 .../126-python3-sphinx-rtd-theme_2.0.0+dfsg-1_all.deb ... Unpacking python3-sphinx-rtd-theme (2.0.0+dfsg-1) ... Selecting previously unselected package python3-sphinxcontrib.spelling. Preparing to unpack .../127-python3-sphinxcontrib.spelling_7.7.0-1_all.deb ... Unpacking python3-sphinxcontrib.spelling (7.7.0-1) ... Selecting previously unselected package python3-tabulate. Preparing to unpack .../128-python3-tabulate_0.8.10-1_all.deb ... Unpacking python3-tabulate (0.8.10-1) ... Selecting previously unselected package python3-xlrd. Preparing to unpack .../129-python3-xlrd_2.0.1-2_all.deb ... Unpacking python3-xlrd (2.0.1-2) ... Selecting previously unselected package python3-xlwt. Preparing to unpack .../130-python3-xlwt_1.3.0-4_all.deb ... Unpacking python3-xlwt (1.3.0-4) ... Selecting previously unselected package python3-tablib. Preparing to unpack .../131-python3-tablib_3.6.0-1_all.deb ... Unpacking python3-tablib (3.6.0-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:armhf (1.5.7-2) ... Setting up libtext-iconv-perl:armhf (1.7-8+b3) ... Setting up libkeyutils1:armhf (1.6.3-3) ... 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 libyaml-0-2:armhf (0.2.5-1+b1) ... Setting up libaspell15:armhf (0.60.8.1-1+b1) ... 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 libcom-err2:armhf (1.47.1~rc2-1) ... 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 libkrb5support0:armhf (1.20.1-6+b1) ... Setting up libsasl2-modules-db:armhf (2.1.28+dfsg1-6) ... Setting up tzdata (2024a-4) ... Current default time zone: 'Etc/UTC' Local time is now: Fri May 10 22:19:37 UTC 2024. Universal Time is now: Fri May 10 22:19:37 UTC 2024. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up libglib2.0-0t64:armhf (2.80.1-1) ... No schema files found: doing nothing. Setting up libblas3:armhf (3.12.0-3) ... update-alternatives: using /usr/lib/arm-linux-gnueabihf/blas/libblas.so.3 to provide /usr/lib/arm-linux-gnueabihf/libblas.so.3 (libblas.so.3-arm-linux-gnueabihf) in auto mode Setting up emacsen-common (3.0.5) ... Setting up autopoint (0.21-14) ... Setting up libk5crypto3:armhf (1.20.1-6+b1) ... Setting up libsasl2-2:armhf (2.1.28+dfsg1-6) ... Setting up libgfortran5:armhf (14-20240330-1) ... 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 libkrb5-3:armhf (1.20.1-6+b1) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up libhunspell-1.7-0:armhf (1.7.2+really1.7.2-10+b2) ... 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 liblapack3:armhf (3.12.0-3) ... update-alternatives: using /usr/lib/arm-linux-gnueabihf/lapack/liblapack.so.3 to provide /usr/lib/arm-linux-gnueabihf/liblapack.so.3 (liblapack.so.3-arm-linux-gnueabihf) in auto mode Setting up gettext (0.21-14+b1) ... Setting up dictionaries-common (1.29.7) ... Setting up libtool (2.4.7-7) ... Setting up libldap-2.5-0:armhf (2.5.17+dfsg-1) ... 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 python3.11-doc (3.11.9-1) ... Setting up libgssapi-krb5-2:armhf (1.20.1-6+b1) ... 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 libxslt1.1:armhf (1.1.35-1+b1) ... Setting up hunspell-en-us (1:2020.12.07-2) ... Setting up python-django-doc (3:4.2.11-1) ... Setting up python3-doc (3.11.8-1) ... Setting up libpython3.12-stdlib:armhf (3.12.3-1) ... Setting up libenchant-2-2:armhf (2.3.3-2+b2) ... 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 libpq5:armhf (16.2-2+b1) ... 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-tz (2024.1-2) ... 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-enchant (3.2.2-1) ... Setting up python3-certifi (2023.11.17-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up python3-mdurl (0.1.2-1) ... Setting up python3-xlwt (1.3.0-4) ... Setting up python3-idna (3.6-2) ... Setting up python3-psycopg2 (2.9.9-1+b1) ... Setting up python3-urllib3 (1.26.18-2) ... Setting up python3-markdown-it (3.0.0-2) ... Setting up python3-lxml:armhf (5.1.0-1) ... Setting up python3-et-xmlfile (1.0.1-2.1) ... Setting up python3-xlrd (2.0.1-2) ... Setting up python3-dateutil (2.9.0-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-commonmark (0.9.1-6) ... 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-more-itertools (10.2.0-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-defusedxml (0.7.1-2) ... Setting up python3-charset-normalizer (3.3.2-1) ... Setting up python3-alabaster (0.7.12-1) ... Setting up python3-mdit-py-plugins (0.4.0-1) ... Setting up python3-tabulate (0.8.10-1) ... Setting up python3-all (3.11.8-1) ... Setting up python3-yaml (6.0.1-2) ... Setting up python3-zipp (1.0.0-6) ... Setting up python3-pygments (2.17.2+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-openpyxl (3.1.2+dfsg-6) ... Setting up python3-requests (2.31.0+dfsg-1) ... Setting up python3-numpy (1:1.26.4+ds-8) ... Setting up python3-fudge (1.1.1-2) ... Setting up python3-django-filters (24.2-1) ... Setting up python3-odf (1.4.2-2) ... Setting up dh-python (6.20240422) ... Setting up python3-importlib-metadata (4.12.0-1) ... Setting up python3-pandas-lib:armhf (2.1.4+dfsg-8) ... Setting up python3-pandas (2.1.4+dfsg-8) ... Setting up python3-tablib (3.6.0-1) ... 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-myst-parser (3.0.1-1) ... Setting up python3-sphinxcontrib.spelling (7.7.0-1) ... Setting up python3-recommonmark (0.7.1+ds-5) ... /usr/lib/python3/dist-packages/recommonmark/transform.py:254: SyntaxWarning: invalid escape sequence '\w' match = re.search('[ ]?[\w_-]+::.*', language) Setting up python3-sphinxcontrib.jquery (4.1-5) ... Setting up python3-sphinx-rtd-theme (2.0.0+dfsg-1) ... Processing triggers for dictionaries-common (1.29.7) ... 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/django-tables-2.7.0/ && 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 > ../django-tables_2.7.0-2_source.changes dpkg-buildpackage: info: source package django-tables dpkg-buildpackage: info: source version 2.7.0-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Alexandre Detiste dpkg-source --before-build . dpkg-buildpackage: info: host architecture armhf dpkg-source: info: using options from django-tables-2.7.0/debian/source/options: --extend-diff-ignore=^(\.project|\.pydevproject)$ debian/rules clean dh clean --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/build/reproducible-path/django-tables-2.7.0' dh_auto_clean I: pybuild base:311: python3.12 setup.py clean running clean removing '/build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/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 running clean removing '/build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/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 rm -f -r .cache django_tables2.egg-info rm -f docs/pages/CHANGELOG.md make[1]: Leaving directory '/build/reproducible-path/django-tables-2.7.0' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --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 running config I: pybuild base:311: python3.11 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3.12 setup.py build running build running build_py creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/utils.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/tables.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/paginators.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/data.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/views.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/rows.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 copying django_tables2/config.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templatetags copying django_tables2/templatetags/django_tables2.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templatetags copying django_tables2/templatetags/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templatetags creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/timecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/urlcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/manytomanycolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/base.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/jsoncolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/linkcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/booleancolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/checkboxcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/datecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/datetimecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/filecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/templatecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns copying django_tables2/columns/emailcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export copying django_tables2/export/views.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export copying django_tables2/export/export.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export copying django_tables2/export/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export running egg_info creating django_tables2.egg-info writing django_tables2.egg-info/PKG-INFO writing dependency_links to django_tables2.egg-info/dependency_links.txt writing requirements to django_tables2.egg-info/requires.txt writing top-level names to django_tables2.egg-info/top_level.txt writing manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'docs/pages/CHANGELOG.md' warning: no previously-included files matching '*' found under directory 'docs/_build' adding license file 'LICENSE' writing manifest file 'django_tables2.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_tables2.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.pt_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_tables2.locale.pt_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_tables2.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.pt_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_tables2.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.css' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.img' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.templates.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.templates.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.templates.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.templates.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.templates.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/cs creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES copying django_tables2/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES copying django_tables2/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/de creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/de/LC_MESSAGES copying django_tables2/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/de/LC_MESSAGES copying django_tables2/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/de/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/el creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/el/LC_MESSAGES copying django_tables2/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/el/LC_MESSAGES copying django_tables2/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/el/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/en creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/en/LC_MESSAGES copying django_tables2/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/en/LC_MESSAGES copying django_tables2/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/en/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/es creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/es/LC_MESSAGES copying django_tables2/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/es/LC_MESSAGES copying django_tables2/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/es/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fa creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES copying django_tables2/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES copying django_tables2/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fr creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES copying django_tables2/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES copying django_tables2/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/hu creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES copying django_tables2/locale/hu/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES copying django_tables2/locale/hu/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/it creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/it/LC_MESSAGES copying django_tables2/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/it/LC_MESSAGES copying django_tables2/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/it/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/lt creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES copying django_tables2/locale/lt/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES copying django_tables2/locale/lt/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nb creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES copying django_tables2/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES copying django_tables2/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nl creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES copying django_tables2/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES copying django_tables2/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pl creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES copying django_tables2/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES copying django_tables2/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_BR creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES copying django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES copying django_tables2/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_PT creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES copying django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES copying django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/ru creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES copying django_tables2/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES copying django_tables2/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/sv creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES copying django_tables2/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES copying django_tables2/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/uk creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES copying django_tables2/locale/uk/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES copying django_tables2/locale/uk/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/zh_Hans creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES copying django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES copying django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2 copying django_tables2/static/django_tables2/bootstrap.css -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/css copying django_tables2/static/django_tables2/themes/paleblue/css/screen.css -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/css creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-down.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-up.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-down.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-up.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/false.gif -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/header-bg.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/missing.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/pagination-bg.gif -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/true.gif -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap-responsive.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap4-responsive.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap4.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap5-responsive.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap5.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/semantic.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/table.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2 I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/utils.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/tables.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/paginators.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/data.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/views.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/rows.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 copying django_tables2/config.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templatetags copying django_tables2/templatetags/django_tables2.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templatetags copying django_tables2/templatetags/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templatetags creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/timecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/urlcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/manytomanycolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/base.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/jsoncolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/linkcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/booleancolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/checkboxcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/datecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/datetimecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/filecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/templatecolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns copying django_tables2/columns/emailcolumn.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export copying django_tables2/export/views.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export copying django_tables2/export/export.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export copying django_tables2/export/__init__.py -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export running egg_info writing django_tables2.egg-info/PKG-INFO writing dependency_links to django_tables2.egg-info/dependency_links.txt writing requirements to django_tables2.egg-info/requires.txt writing top-level names to django_tables2.egg-info/top_level.txt reading manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'docs/pages/CHANGELOG.md' warning: no previously-included files matching '*' found under directory 'docs/_build' adding license file 'LICENSE' writing manifest file 'django_tables2.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_tables2.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.pt_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_tables2.locale.pt_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_tables2.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.pt_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_tables2.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.css' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.img' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.templates.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.templates.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.templates.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.templates.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.templates.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/cs creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES copying django_tables2/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES copying django_tables2/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/de creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/de/LC_MESSAGES copying django_tables2/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/de/LC_MESSAGES copying django_tables2/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/de/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/el creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/el/LC_MESSAGES copying django_tables2/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/el/LC_MESSAGES copying django_tables2/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/el/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/en creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/en/LC_MESSAGES copying django_tables2/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/en/LC_MESSAGES copying django_tables2/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/en/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/es creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/es/LC_MESSAGES copying django_tables2/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/es/LC_MESSAGES copying django_tables2/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/es/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fa creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES copying django_tables2/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES copying django_tables2/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fr creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES copying django_tables2/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES copying django_tables2/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/hu creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES copying django_tables2/locale/hu/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES copying django_tables2/locale/hu/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/it creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/it/LC_MESSAGES copying django_tables2/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/it/LC_MESSAGES copying django_tables2/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/it/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/lt creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES copying django_tables2/locale/lt/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES copying django_tables2/locale/lt/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nb creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES copying django_tables2/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES copying django_tables2/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nl creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES copying django_tables2/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES copying django_tables2/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pl creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES copying django_tables2/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES copying django_tables2/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_BR creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES copying django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES copying django_tables2/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_PT creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES copying django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES copying django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/ru creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES copying django_tables2/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES copying django_tables2/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/sv creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES copying django_tables2/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES copying django_tables2/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/uk creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES copying django_tables2/locale/uk/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES copying django_tables2/locale/uk/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/zh_Hans creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES copying django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES copying django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2 copying django_tables2/static/django_tables2/bootstrap.css -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/css copying django_tables2/static/django_tables2/themes/paleblue/css/screen.css -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/css creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-down.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-up.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-down.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-up.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/false.gif -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/header-bg.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/missing.png -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/pagination-bg.gif -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/true.gif -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates creating /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap-responsive.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap4-responsive.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap4.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap5-responsive.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap5.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/semantic.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/table.html -> /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2 debian/rules override_dh_auto_test make[1]: Entering directory '/build/reproducible-path/django-tables-2.7.0' dh_auto_test -- --system=custom --test-args="{interpreter} -Wd manage.py test" I: pybuild base:311: python3.12 -Wd manage.py test Creating test database for alias 'default'... Found 376 test(s). System check identified no issues (0 silenced). ......................................................................................................................................................................./usr/lib/python3/dist-packages/django/conf/__init__.py:336: RemovedInDjango50Warning: The USE_L10N setting is deprecated. Starting with Django 5.0, localized formatting of data will always be enabled. For example Django will display numbers and dates using the format of the current locale. warnings.warn(USE_L10N_DEPRECATED_MSG, RemovedInDjango50Warning) ....................................../usr/lib/python3.12/unittest/case.py:589: DeprecationWarning: Use '__' to separate path components, not '.' in accessor 'a.b' (fallback will be removed in django_tables2 version 3). if method() is not None: ........................................................................................................................................................................... ---------------------------------------------------------------------- Ran 376 tests in 2.607s OK Destroying test database for alias 'default'... I: pybuild base:311: python3.11 -Wd manage.py test Creating test database for alias 'default'... Found 376 test(s). System check identified no issues (0 silenced). ......................................................................................................................................................................./usr/lib/python3/dist-packages/django/conf/__init__.py:336: RemovedInDjango50Warning: The USE_L10N setting is deprecated. Starting with Django 5.0, localized formatting of data will always be enabled. For example Django will display numbers and dates using the format of the current locale. warnings.warn(USE_L10N_DEPRECATED_MSG, RemovedInDjango50Warning) ....................................../usr/lib/python3.11/unittest/case.py:579: DeprecationWarning: Use '__' to separate path components, not '.' in accessor 'a.b' (fallback will be removed in django_tables2 version 3). if method() is not None: ........................................................................................................................................................................... ---------------------------------------------------------------------- Ran 376 tests in 3.018s OK Destroying test database for alias 'default'... make[1]: Leaving directory '/build/reproducible-path/django-tables-2.7.0' create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3.12 setup.py install --root /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2 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 django_tables2.egg-info/PKG-INFO writing dependency_links to django_tables2.egg-info/dependency_links.txt writing requirements to django_tables2.egg-info/requires.txt writing top-level names to django_tables2.egg-info/top_level.txt reading manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'docs/pages/CHANGELOG.md' warning: no previously-included files matching '*' found under directory 'docs/_build' adding license file 'LICENSE' writing manifest file 'django_tables2.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_tables2.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.pt_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_tables2.locale.pt_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_tables2.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.pt_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_tables2.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.css' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.img' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.templates.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.templates.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.templates.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.templates.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.templates.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) running install_lib creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/utils.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/tables.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pl creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/cs creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/cs/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/cs/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/cs/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fr creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fr/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fr/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fr/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nb creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nb/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nb/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nb/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/ru creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/ru/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/ru/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/ru/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_BR creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/it creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/it/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/it/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/it/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/sv creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/sv/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/sv/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/sv/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/es creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/es/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/es/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/es/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_PT creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/hu creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/hu/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/hu/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/hu/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/lt creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/lt/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/lt/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/lt/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/de creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/de/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/de/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/de/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/en creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/en/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/en/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/en/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/zh_Hans creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nl creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/nl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/el creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/el/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/el/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/el/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fa creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fa/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fa/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/fa/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/uk creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/uk/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/uk/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/locale/uk/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/paginators.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templatetags copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templatetags/django_tables2.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templatetags copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templatetags/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templatetags copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/data.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/views.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/bootstrap.css -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/header-bg.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-down.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/pagination-bg.gif -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-up.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-down.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/false.gif -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/true.gif -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-up.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/missing.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/css copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/css/screen.css -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/static/django_tables2/themes/paleblue/css creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/table.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/bootstrap5.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/bootstrap-responsive.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/bootstrap4.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/bootstrap.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/bootstrap5-responsive.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/bootstrap4-responsive.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/templates/django_tables2/semantic.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/rows.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/timecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/urlcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/manytomanycolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/base.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/jsoncolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/linkcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/booleancolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/checkboxcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/datecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/datetimecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/filecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/templatecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/columns/emailcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/config.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export/views.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export/export.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.12_django-tables2/build/django_tables2/export/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/utils.py to utils.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/tables.py to tables.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/paginators.py to paginators.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templatetags/django_tables2.py to django_tables2.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/templatetags/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/data.py to data.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/rows.py to rows.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/timecolumn.py to timecolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/urlcolumn.py to urlcolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/manytomanycolumn.py to manytomanycolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/base.py to base.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/jsoncolumn.py to jsoncolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/linkcolumn.py to linkcolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/booleancolumn.py to booleancolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/checkboxcolumn.py to checkboxcolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/datecolumn.py to datecolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/datetimecolumn.py to datetimecolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/filecolumn.py to filecolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/templatecolumn.py to templatecolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/columns/emailcolumn.py to emailcolumn.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/config.py to config.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export/views.py to views.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export/export.py to export.cpython-312.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2/export/__init__.py to __init__.cpython-312.pyc running install_egg_info Copying django_tables2.egg-info to /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.12/dist-packages/django_tables2-2.7.0.egg-info Skipping SOURCES.txt running install_scripts I: pybuild pybuild:334: rm -rf /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python*/dist-packages/django_tables2/static/django_tables2 I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2 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 django_tables2.egg-info/PKG-INFO writing dependency_links to django_tables2.egg-info/dependency_links.txt writing requirements to django_tables2.egg-info/requires.txt writing top-level names to django_tables2.egg-info/top_level.txt reading manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'docs/pages/CHANGELOG.md' warning: no previously-included files matching '*' found under directory 'docs/_build' adding license file 'LICENSE' writing manifest file 'django_tables2.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_tables2.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.pt_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_tables2.locale.pt_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_tables2.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.pt_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_tables2.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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_tables2.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.css' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.static.django_tables2.themes.paleblue.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.img' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no 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_tables2.templates.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.templates.django_tables2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.templates.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.templates.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.templates.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) running install_lib creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/utils.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/tables.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pl creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/cs creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/cs/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/cs/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/cs/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/cs/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fr creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fr/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fr/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fr/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fr/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nb creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nb/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nb/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nb/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nb/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/ru creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/ru/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/ru/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/ru/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/ru/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_BR creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/it creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/it/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/it/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/it/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/it/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/it/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/sv creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/sv/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/sv/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/sv/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/sv/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/es creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/es/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/es/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/es/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/es/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/es/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_PT creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/hu creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/hu/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/hu/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/hu/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/hu/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/lt creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/lt/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/lt/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/lt/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/lt/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/de creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/de/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/de/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/de/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/de/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/de/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/en creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/en/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/en/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/en/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/en/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/en/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/zh_Hans creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nl creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nl/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/nl/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/nl/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/el creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/el/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/el/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/el/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/el/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/el/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fa creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fa/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fa/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/fa/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/fa/LC_MESSAGES creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/uk creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/uk/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES/django.po -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/uk/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/locale/uk/LC_MESSAGES/django.mo -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/locale/uk/LC_MESSAGES copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/paginators.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templatetags copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templatetags/django_tables2.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templatetags copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templatetags/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templatetags copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/data.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/views.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/bootstrap.css -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/header-bg.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-down.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/pagination-bg.gif -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-up.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-down.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/false.gif -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/true.gif -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-up.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/img/missing.png -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/img creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/css copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/static/django_tables2/themes/paleblue/css/screen.css -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/static/django_tables2/themes/paleblue/css creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/table.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/bootstrap5.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/bootstrap-responsive.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/bootstrap4.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/bootstrap.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/bootstrap5-responsive.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/bootstrap4-responsive.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/templates/django_tables2/semantic.html -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templates/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/rows.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/timecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/urlcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/manytomanycolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/base.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/jsoncolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/linkcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/booleancolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/checkboxcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/datecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/datetimecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/filecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/templatecolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/columns/emailcolumn.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/config.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2 creating /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export/views.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export/export.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export copying /build/reproducible-path/django-tables-2.7.0/.pybuild/cpython3_3.11_django-tables2/build/django_tables2/export/__init__.py -> /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/utils.py to utils.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/tables.py to tables.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/paginators.py to paginators.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templatetags/django_tables2.py to django_tables2.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/data.py to data.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/views.py to views.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/rows.py to rows.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/timecolumn.py to timecolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/urlcolumn.py to urlcolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/manytomanycolumn.py to manytomanycolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/base.py to base.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/jsoncolumn.py to jsoncolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/linkcolumn.py to linkcolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/booleancolumn.py to booleancolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/checkboxcolumn.py to checkboxcolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/datecolumn.py to datecolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/datetimecolumn.py to datetimecolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/filecolumn.py to filecolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/templatecolumn.py to templatecolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/columns/emailcolumn.py to emailcolumn.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/config.py to config.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export/views.py to views.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export/export.py to export.cpython-311.pyc byte-compiling /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2/export/__init__.py to __init__.cpython-311.pyc running install_egg_info Copying django_tables2.egg-info to /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python3.11/dist-packages/django_tables2-2.7.0.egg-info Skipping SOURCES.txt running install_scripts I: pybuild pybuild:334: rm -rf /build/reproducible-path/django-tables-2.7.0/debian/python3-django-tables2/usr/lib/python*/dist-packages/django_tables2/static/django_tables2 dh_install -O--buildsystem=pybuild dh_installdocs -O--buildsystem=pybuild debian/rules override_dh_sphinxdoc make[1]: Entering directory '/build/reproducible-path/django-tables-2.7.0' PYTHONPATH={build_dir} \ python3 -m sphinx -b html -E -N -D html_last_updated_fmt="28 February 2024" docs /build/reproducible-path/django-tables-2.7.0/debian/python-django-tables2-doc/usr/share/doc/python-django-tables2-doc/html Running Sphinx v7.2.6 Initializing Spelling Checker 7.7.0 making output directory... done loading intersphinx inventory from /usr/share/doc/python3-doc/html/objects.inv... loading intersphinx inventory from /usr/share/doc/python-django-doc/html/objects.inv... myst v3.0.1: MdParserConfig(commonmark_only=False, gfm_only=False, enable_extensions=set(), disable_syntax=[], all_links_external=False, links_external_new_tab=False, url_schemes=('http', 'https', 'mailto', 'ftp'), ref_domains=None, fence_as_directive=set(), number_code_blocks=[], title_to_header=False, heading_anchors=3, heading_slug_func=None, html_meta={}, footnote_transition=True, words_per_minute=200, substitutions={}, linkify_fuzzy_links=True, dmath_allow_labels=True, dmath_allow_space=True, dmath_allow_digits=True, dmath_double_inline=False, update_mathjax=True, mathjax_classes='tex2jax_process|mathjax_process|math|output_area', enable_checkboxes=False, suppress_warnings=[], highlight_code_blocks=True) building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 27 source files that are out of date updating environment: [new config] 27 added, 0 changed, 0 removed reading sources... [ 4%] index reading sources... [ 7%] pages/CHANGELOG reading sources... [ 11%] pages/api-reference reading sources... [ 15%] pages/builtin-columns reading sources... [ 19%] pages/column-attributes reading sources... [ 22%] pages/column-headers-and-footers reading sources... [ 26%] pages/custom-data reading sources... [ 30%] pages/custom-rendering reading sources... [ 33%] pages/export reading sources... [ 37%] pages/faq reading sources... [ 41%] pages/filtering reading sources... [ 44%] pages/generic-mixins reading sources... [ 48%] pages/glossary reading sources... [ 52%] pages/installation reading sources... [ 56%] pages/internal reading sources... [ 59%] pages/localization-control reading sources... [ 63%] pages/ordering reading sources... [ 67%] pages/pagination reading sources... [ 70%] pages/pinned-rows reading sources... [ 74%] pages/query-string-fields reading sources... [ 78%] pages/reference reading sources... [ 81%] pages/swapping-columns reading sources... [ 85%] pages/table-data reading sources... [ 89%] pages/table-mixins reading sources... [ 93%] pages/template-tags reading sources... [ 96%] pages/tutorial reading sources... [100%] pages/upgrade-changelog 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... [ 4%] index writing output... [ 7%] pages/CHANGELOG writing output... [ 11%] pages/api-reference writing output... [ 15%] pages/builtin-columns writing output... [ 19%] pages/column-attributes writing output... [ 22%] pages/column-headers-and-footers writing output... [ 26%] pages/custom-data writing output... [ 30%] pages/custom-rendering writing output... [ 33%] pages/export writing output... [ 37%] pages/faq writing output... [ 41%] pages/filtering writing output... [ 44%] pages/generic-mixins writing output... [ 48%] pages/glossary writing output... [ 52%] pages/installation writing output... [ 56%] pages/internal writing output... [ 59%] pages/localization-control writing output... [ 63%] pages/ordering writing output... [ 67%] pages/pagination writing output... [ 70%] pages/pinned-rows writing output... [ 74%] pages/query-string-fields writing output... [ 78%] pages/reference writing output... [ 81%] pages/swapping-columns writing output... [ 85%] pages/table-data writing output... [ 89%] pages/table-mixins writing output... [ 93%] pages/template-tags writing output... [ 96%] pages/tutorial writing output... [100%] pages/upgrade-changelog generating indices... genindex done highlighting module code... [ 5%] django_tables2.columns.base highlighting module code... [ 10%] django_tables2.columns.booleancolumn highlighting module code... [ 14%] django_tables2.columns.checkboxcolumn highlighting module code... [ 19%] django_tables2.columns.datecolumn highlighting module code... [ 24%] django_tables2.columns.datetimecolumn highlighting module code... [ 29%] django_tables2.columns.emailcolumn highlighting module code... [ 33%] django_tables2.columns.filecolumn highlighting module code... [ 38%] django_tables2.columns.jsoncolumn highlighting module code... [ 43%] django_tables2.columns.linkcolumn highlighting module code... [ 48%] django_tables2.columns.manytomanycolumn highlighting module code... [ 52%] django_tables2.columns.templatecolumn highlighting module code... [ 57%] django_tables2.columns.urlcolumn highlighting module code... [ 62%] django_tables2.config highlighting module code... [ 67%] django_tables2.data highlighting module code... [ 71%] django_tables2.export.export highlighting module code... [ 76%] django_tables2.export.views highlighting module code... [ 81%] django_tables2.paginators highlighting module code... [ 86%] django_tables2.rows highlighting module code... [ 90%] django_tables2.tables highlighting module code... [ 95%] django_tables2.utils highlighting module code... [100%] django_tables2.views writing additional pages... search done copying images... [ 50%] _static/tutorial.png copying images... [100%] _static/tutorial-bootstrap.png dumping search index in English (code: en)... done dumping object inventory... done build succeeded. The HTML pages are in debian/python-django-tables2-doc/usr/share/doc/python-django-tables2-doc/html. # docs/conf.py generates a symlink of the CHANGELOG to docs/pages/CHANGELOG rm -f -r /build/reproducible-path/django-tables-2.7.0/debian/python-django-tables2-doc/usr/share/doc/python-django-tables2-doc/html/pages/CHANGELOG dh_sphinxdoc make[1]: Leaving directory '/build/reproducible-path/django-tables-2.7.0' dh_installchangelogs -O--buildsystem=pybuild debian/rules override_dh_installexamples make[1]: Entering directory '/build/reproducible-path/django-tables-2.7.0' dh_installexamples -A -X__pycache__ dh_installexamples: warning: Cannot auto-detect main package for python-django-tables2-doc. If the default is wrong, please use --doc-main-package make[1]: Leaving directory '/build/reproducible-path/django-tables-2.7.0' 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-tables2/usr/lib/python3/dist-packages/django_tables2/locale/pl/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/cs/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/fr/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/nb/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/ru/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/pt_BR/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/it/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/sv/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/es/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/pt_PT/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/hu/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/lt/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/de/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/en/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/nl/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/el/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/fa/LC_MESSAGES/django.mo Normalized debian/python3-django-tables2/usr/lib/python3/dist-packages/django_tables2/locale/uk/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-tables2-doc: substitution variable ${sphinxdoc:Built-Using} unused, but is defined dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'python3-django-tables2' in '../python3-django-tables2_2.7.0-2_all.deb'. dpkg-deb: building package 'python-django-tables2-doc' in '../python-django-tables2-doc_2.7.0-2_all.deb'. dpkg-genbuildinfo --build=binary -O../django-tables_2.7.0-2_armhf.buildinfo dpkg-genchanges --build=binary -O../django-tables_2.7.0-2_armhf.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-source: info: using options from django-tables-2.7.0/debian/source/options: --extend-diff-ignore=^(\.project|\.pydevproject)$ dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: not including original 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/1017 and its subdirectories I: Current time: Fri May 10 10:25:59 -12 2024 I: pbuilder-time-stamp: 1715379959 Fri May 10 22:26:12 UTC 2024 I: 1st build successful. Starting 2nd build on remote node virt64z-armhf-rb.debian.net. Fri May 10 22:26:12 UTC 2024 I: Preparing to do remote build '2' on virt64z-armhf-rb.debian.net. Fri May 10 22:30:04 UTC 2024 I: Deleting $TMPDIR on virt64z-armhf-rb.debian.net. Fri May 10 22:30:07 UTC 2024 I: django-tables_2.7.0-2_armhf.changes: Format: 1.8 Date: Wed, 28 Feb 2024 19:55:48 +0100 Source: django-tables Binary: python-django-tables2-doc python3-django-tables2 Architecture: all Version: 2.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Alexandre Detiste Description: python-django-tables2-doc - Table/data-grid framework for Django (Documentation) python3-django-tables2 - Table/data-grid framework for Django (Python 3) Changes: django-tables (2.7.0-2) unstable; urgency=medium . * Team upload. * Remove build-dependency on python3-mock Checksums-Sha1: 466edd8926f1150c01b34aebb23284b20b3799fe 8983 django-tables_2.7.0-2_armhf.buildinfo 2fe9c31dd87507fed18fee3b17ad669bebb8dd90 235352 python-django-tables2-doc_2.7.0-2_all.deb e20123e842ca8c9a37d38aec5427ef3321f422d6 66300 python3-django-tables2_2.7.0-2_all.deb Checksums-Sha256: a851ccc4bc0ec9c14ffdd49ac00c5533d4d3e3c94c39ceca3c22cd7f19955b0f 8983 django-tables_2.7.0-2_armhf.buildinfo 3caa51f4804dc56ea5be62b0367bd63e0289e6ce610b6cb7eb3c11161bccaedd 235352 python-django-tables2-doc_2.7.0-2_all.deb 3bf323dcf4a08d31611695a84b6bbe761ece574ec62460bd72baa7aacbd4ba54 66300 python3-django-tables2_2.7.0-2_all.deb Files: e5222154cdbedaa257fafc7d644059f1 8983 python optional django-tables_2.7.0-2_armhf.buildinfo 27e1b679776f8a084013b1717c4b7611 235352 doc optional python-django-tables2-doc_2.7.0-2_all.deb 79a54d3c13b06f4939a95399bae4b58d 66300 python optional python3-django-tables2_2.7.0-2_all.deb Fri May 10 22:30:08 UTC 2024 I: diffoscope 265 will be used to compare the two builds: Running as unit: rb-diffoscope-armhf_9-5330.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.1R9xE7xx/django-tables_2.7.0-2.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.1R9xE7xx/django-tables_2.7.0-2.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.1R9xE7xx/django-tables_2.7.0-2.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.1R9xE7xx/b1/django-tables_2.7.0-2_armhf.changes /srv/reproducible-results/rbuild-debian/r-b-build.1R9xE7xx/b2/django-tables_2.7.0-2_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.372s) 0.372s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.020s) 0.020s 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: 713ms CPU time consumed: 713ms Fri May 10 22:30:10 UTC 2024 I: diffoscope 265 found no differences in the changes files, and a .buildinfo file also exists. Fri May 10 22:30:10 UTC 2024 I: django-tables from trixie built successfully and reproducibly on armhf. Fri May 10 22:30:12 UTC 2024 I: Submitting .buildinfo files to external archives: Fri May 10 22:30:12 UTC 2024 I: Submitting 12K b1/django-tables_2.7.0-2_armhf.buildinfo.asc Fri May 10 22:30:12 UTC 2024 I: Submitting 12K b2/django-tables_2.7.0-2_armhf.buildinfo.asc Fri May 10 22:30:14 UTC 2024 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Fri May 10 22:30:14 UTC 2024 I: Done submitting .buildinfo files. Fri May 10 22:30:14 UTC 2024 I: Removing signed django-tables_2.7.0-2_armhf.buildinfo.asc files: removed './b1/django-tables_2.7.0-2_armhf.buildinfo.asc' removed './b2/django-tables_2.7.0-2_armhf.buildinfo.asc'