Wed May 22 13:26:12 UTC 2024 I: starting to build glances/trixie/armhf on jenkins on '2024-05-22 13:26' Wed May 22 13:26:12 UTC 2024 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/armhf_14/4824/console.log Wed May 22 13:26:12 UTC 2024 I: Downloading source for trixie/glances=4.0.5+dfsg-1 --2024-05-22 13:26:12-- http://deb.debian.org/debian/pool/main/g/glances/glances_4.0.5%2bdfsg-1.dsc Connecting to 46.16.76.132:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2171 (2.1K) [text/prs.lines.tag] Saving to: ‘glances_4.0.5+dfsg-1.dsc’ 0K .. 100% 307M=0s 2024-05-22 13:26:12 (307 MB/s) - ‘glances_4.0.5+dfsg-1.dsc’ saved [2171/2171] Wed May 22 13:26:12 UTC 2024 I: glances_4.0.5+dfsg-1.dsc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: glances Binary: glances, glances-doc Architecture: all Version: 4.0.5+dfsg-1 Maintainer: Daniel Echeverri Uploaders: Sebastien Badia Homepage: https://github.com/nicolargo/glances Standards-Version: 4.7.0 Vcs-Browser: https://salsa.debian.org/debian/glances Vcs-Git: https://salsa.debian.org/debian/glances.git Testsuite: autopkgtest Testsuite-Triggers: curl Build-Depends: debhelper-compat (= 13), dh-python, python3-all, python3-psutil, python3-setuptools, python3-sphinx, python3-defusedxml, python3-sphinx-rtd-theme, python3-ujson Package-List: glances deb utils optional arch=all glances-doc deb doc optional arch=all Checksums-Sha1: bb51cfdb70fa8c57a3e4e42c49c7b09c4da88b27 6441210 glances_4.0.5+dfsg.orig.tar.gz 5e3b36bbbb523b21e3615a679fcb0ff0e1a8567a 12372 glances_4.0.5+dfsg-1.debian.tar.xz Checksums-Sha256: 91d1deb4e013a789174a719bfc9e96dc9c86fdf513f1ec459c7dcc79d2ceaf39 6441210 glances_4.0.5+dfsg.orig.tar.gz b76bcf7c9bce9b7442f23e97c55b9aaad3298a28a8c28efbc08682c2d92decda 12372 glances_4.0.5+dfsg-1.debian.tar.xz Files: fa1aadc4d3b908707e8518021f6dffc1 6441210 glances_4.0.5+dfsg.orig.tar.gz 72e0c159847bd9891fd85383fa30d0c1 12372 glances_4.0.5+dfsg-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAmZKzdMTHGVwc2lsb25A ZGViaWFuLm9yZwAKCRAh/ClQS1Iw23J9D/sFepI35wSeBodCQd8PesYG03JsyZrD 6g6mZ6LMS3nYlelRYgs5GSe9HX4hiXy4a0Jiw74Eesi+mNXks+53ECHOTSLcqkL8 nyW2pemPZ2pFsah+bV+X2nR8MTPUWqnk8d9OamF0mpMgzjO9SftRL6hmMhBS/gma 2XPbX9BXVNmsIR5SCO5x2iq00YDTFUTQJrM4D2HVfq5/C0gkawpCWi/BqCheBzt6 M4ChSg3bqT0wC3Ak+QXX6eKo3IvkkLeHzFjXYxwMMjc5IzcEfELPJljTHYh+Smfx 42Qch/dfFVasFqBYsylolu3moO0o2fe85t5KOGosZ+IbhLTaFlUkW++KJFEH/U0R x5W+9da+53ZzTKpvcnFfaRF8PFIA5yqi+G7Au5hqwd1EthmAnwxmcaZrhtGFmSSX HVxC1r9xOcJptZwhElfHTW/8E44dTIRZixQM/N8Ud3r/Inj0GWPIqhAmFjuCBk/m hF4C+c+D61VYdAq/iCKQMupB4VpEyRUmYBDi6C4Z4TrTkJWSWUxvJrjfCZ1K3AN9 ajpt3xOgS+pQk7dSL+9U6hm1UGYVZa0Wj4L3AjJuGcL9s0xyr4YHGLFJ1EMsil5v HQzVt36ZIdEFK+ieBiGn2NPVdOhFWwW02tkYpil26/pWUlPJho3GiHvbIf/1OMVU WNpmLFAwIuwhmg== =fZsq -----END PGP SIGNATURE----- Wed May 22 13:26:12 UTC 2024 I: Checking whether the package is not for us Wed May 22 13:26:12 UTC 2024 I: Starting 1st build on remote node virt32z-armhf-rb.debian.net. Wed May 22 13:26:12 UTC 2024 I: Preparing to do remote build '1' on virt32z-armhf-rb.debian.net. Wed May 22 13:28:46 UTC 2024 I: Deleting $TMPDIR on virt32z-armhf-rb.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Wed May 22 01:26:18 -12 2024 I: pbuilder-time-stamp: 1716384378 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 [glances_4.0.5+dfsg-1.dsc] I: copying [./glances_4.0.5+dfsg.orig.tar.gz] I: copying [./glances_4.0.5+dfsg-1.debian.tar.xz] I: Extracting source gpgv: Signature made Mon May 20 04:13:07 2024 gpgv: using RSA key D0D085B169C3BFD9404858FA21FC29504B5230DB gpgv: issuer "epsilon@debian.org" gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./glances_4.0.5+dfsg-1.dsc: no acceptable signature found dpkg-source: info: extracting glances in glances-4.0.5+dfsg dpkg-source: info: unpacking glances_4.0.5+dfsg.orig.tar.gz dpkg-source: info: unpacking glances_4.0.5+dfsg-1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying 002_no_put_links_in_doc.patch dpkg-source: info: applying 003_not_install_static_dir.patch dpkg-source: info: applying 004_disable-pypi.patch dpkg-source: info: applying 006_indicate_user_webserver_static_files_not_included.patch I: Not using root during the build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/4063/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='14c85b32a9ca445492e622d2028ad570' 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='4063' 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.pChifE4P/pbuilderrc_wILL --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.pChifE4P/b1 --logfile b1/build.log glances_4.0.5+dfsg-1.dsc' SUDO_GID='110' SUDO_UID='103' 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 virt32z 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 22 11:24 /bin -> usr/bin I: user script /srv/workspace/pbuilder/4063/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: armhf Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper-compat (= 13), dh-python, python3-all, python3-psutil, python3-setuptools, python3-sphinx, python3-defusedxml, python3-sphinx-rtd-theme, python3-ujson dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 19446 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on debhelper-compat (= 13); however: Package debhelper-compat is not installed. pbuilder-satisfydepends-dummy depends on dh-python; however: Package dh-python is not installed. pbuilder-satisfydepends-dummy depends on python3-all; however: Package python3-all is not installed. pbuilder-satisfydepends-dummy depends on python3-psutil; however: Package python3-psutil is not installed. pbuilder-satisfydepends-dummy depends on python3-setuptools; however: Package python3-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3-sphinx; however: Package python3-sphinx is not installed. pbuilder-satisfydepends-dummy depends on python3-defusedxml; however: Package python3-defusedxml 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-ujson; however: Package python3-ujson is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: autoconf{a} automake{a} autopoint{a} autotools-dev{a} bsdextrautils{a} ca-certificates{a} debhelper{a} dh-autoreconf{a} dh-python{a} dh-strip-nondeterminism{a} docutils-common{a} dwz{a} file{a} fonts-font-awesome{a} fonts-lato{a} gettext{a} gettext-base{a} groff-base{a} intltool-debian{a} libarchive-zip-perl{a} libdata-optlist-perl{a} libdebhelper-perl{a} libdouble-conversion3{a} libelf1t64{a} libexpat1{a} libfile-stripnondeterminism-perl{a} libicu72{a} libjs-jquery{a} libjs-sphinxdoc{a} libjs-underscore{a} libjson-perl{a} libmagic-mgc{a} libmagic1t64{a} libparams-util-perl{a} libpipeline1{a} libpython3-stdlib{a} libpython3.11-minimal{a} libpython3.11-stdlib{a} libpython3.12-minimal{a} libpython3.12-stdlib{a} libreadline8t64{a} libsub-exporter-perl{a} libsub-install-perl{a} libsub-override-perl{a} libsub-prototype-perl{a} libtool{a} libuchardet0{a} libxml2{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} po-debconf{a} python-babel-localedata{a} python3{a} python3-alabaster{a} python3-all{a} python3-babel{a} python3-certifi{a} python3-chardet{a} python3-charset-normalizer{a} python3-defusedxml{a} python3-distutils{a} python3-docutils{a} python3-idna{a} python3-imagesize{a} python3-jinja2{a} python3-lib2to3{a} python3-markupsafe{a} python3-minimal{a} python3-packaging{a} python3-pkg-resources{a} python3-psutil{a} python3-pygments{a} python3-requests{a} python3-roman{a} python3-setuptools{a} python3-six{a} python3-snowballstemmer{a} python3-sphinx{a} python3-sphinx-rtd-theme{a} python3-sphinxcontrib.jquery{a} python3-ujson{a} python3-urllib3{a} python3.11{a} python3.11-minimal{a} python3.12{a} python3.12-minimal{a} readline-common{a} sensible-utils{a} sgml-base{a} sphinx-common{a} sphinx-rtd-theme-common{a} tzdata{a} xml-core{a} The following packages are RECOMMENDED but will NOT be installed: curl javascript-common libarchive-cpio-perl libjson-xs-perl libltdl-dev libmail-sendmail-perl libpaper-utils lynx python3-pil wget 0 packages upgraded, 96 newly installed, 0 to remove and 0 not upgraded. Need to get 46.0 MB of archives. After unpacking 182 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.1-1 [85.8 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 libparams-util-perl armhf 1.102-3 [23.0 kB] Get: 40 http://deb.debian.org/debian trixie/main armhf libsub-install-perl all 0.929-1 [10.5 kB] Get: 41 http://deb.debian.org/debian trixie/main armhf libdata-optlist-perl all 0.114-1 [10.6 kB] Get: 42 http://deb.debian.org/debian trixie/main armhf libsub-exporter-perl all 0.990-1 [50.6 kB] Get: 43 http://deb.debian.org/debian trixie/main armhf libsub-prototype-perl armhf 0.03-2+b2 [9460 B] Get: 44 http://deb.debian.org/debian trixie/main armhf libsub-override-perl all 0.11-1 [10.4 kB] Get: 45 http://deb.debian.org/debian trixie/main armhf libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB] Get: 46 http://deb.debian.org/debian trixie/main armhf dh-strip-nondeterminism all 1.13.1-1 [8620 B] Get: 47 http://deb.debian.org/debian trixie/main armhf libelf1t64 armhf 0.191-1+b1 [183 kB] Get: 48 http://deb.debian.org/debian trixie/main armhf dwz armhf 0.15-1+b2 [106 kB] Get: 49 http://deb.debian.org/debian trixie/main armhf libicu72 armhf 72.1-4+b1 [9070 kB] Get: 50 http://deb.debian.org/debian trixie/main armhf libxml2 armhf 2.9.14+dfsg-1.3+b3 [598 kB] Get: 51 http://deb.debian.org/debian trixie/main armhf gettext armhf 0.21-14+b1 [1230 kB] Get: 52 http://deb.debian.org/debian trixie/main armhf intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 53 http://deb.debian.org/debian trixie/main armhf po-debconf all 1.0.21+nmu1 [248 kB] Get: 54 http://deb.debian.org/debian trixie/main armhf debhelper all 13.15.3 [901 kB] Get: 55 http://deb.debian.org/debian trixie/main armhf python3-pkg-resources all 68.1.2-2 [241 kB] Get: 56 http://deb.debian.org/debian trixie/main armhf python3-lib2to3 all 3.12.3-1 [77.6 kB] Get: 57 http://deb.debian.org/debian trixie/main armhf python3-distutils all 3.12.3-1 [131 kB] Get: 58 http://deb.debian.org/debian trixie/main armhf python3-setuptools all 68.1.2-2 [468 kB] Get: 59 http://deb.debian.org/debian trixie/main armhf dh-python all 6.20240422 [107 kB] Get: 60 http://deb.debian.org/debian trixie/main armhf xml-core all 0.19 [20.1 kB] Get: 61 http://deb.debian.org/debian trixie/main armhf docutils-common all 0.20.1+dfsg-3 [128 kB] Get: 62 http://deb.debian.org/debian trixie/main armhf fonts-font-awesome all 5.0.10+really4.7.0~dfsg-4.1 [517 kB] Get: 63 http://deb.debian.org/debian trixie/main armhf libdouble-conversion3 armhf 3.3.0-1+b1 [38.5 kB] Get: 64 http://deb.debian.org/debian trixie/main armhf libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get: 65 http://deb.debian.org/debian trixie/main armhf libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get: 66 http://deb.debian.org/debian trixie/main armhf libjs-sphinxdoc all 7.2.6-6 [150 kB] Get: 67 http://deb.debian.org/debian trixie/main armhf libjson-perl all 4.10000-1 [87.5 kB] Get: 68 http://deb.debian.org/debian trixie/main armhf libpython3.12-stdlib armhf 3.12.3-1 [1808 kB] Get: 69 http://deb.debian.org/debian trixie/main armhf python-babel-localedata all 2.14.0-1 [5701 kB] Get: 70 http://deb.debian.org/debian trixie/main armhf python3-alabaster all 0.7.12-1 [20.8 kB] Get: 71 http://deb.debian.org/debian trixie/main armhf python3.12 armhf 3.12.3-1 [659 kB] Get: 72 http://deb.debian.org/debian trixie/main armhf python3-all armhf 3.11.8-1 [1056 B] Get: 73 http://deb.debian.org/debian trixie/main armhf python3-babel all 2.14.0-1 [111 kB] Get: 74 http://deb.debian.org/debian trixie/main armhf python3-certifi all 2023.11.17-1 [155 kB] Get: 75 http://deb.debian.org/debian trixie/main armhf python3-chardet all 5.2.0+dfsg-1 [107 kB] Get: 76 http://deb.debian.org/debian trixie/main armhf python3-charset-normalizer all 3.3.2-1 [51.6 kB] Get: 77 http://deb.debian.org/debian trixie/main armhf python3-defusedxml all 0.7.1-2 [43.3 kB] Get: 78 http://deb.debian.org/debian trixie/main armhf python3-roman all 3.3-3 [9880 B] Get: 79 http://deb.debian.org/debian trixie/main armhf python3-docutils all 0.20.1+dfsg-3 [389 kB] Get: 80 http://deb.debian.org/debian trixie/main armhf python3-idna all 3.6-2 [37.0 kB] Get: 81 http://deb.debian.org/debian trixie/main armhf python3-imagesize all 1.4.1-1 [6688 B] Get: 82 http://deb.debian.org/debian trixie/main armhf python3-markupsafe armhf 2.1.5-1 [13.9 kB] Get: 83 http://deb.debian.org/debian trixie/main armhf python3-jinja2 all 3.1.3-1 [119 kB] Get: 84 http://deb.debian.org/debian trixie/main armhf python3-packaging all 24.0-1 [45.5 kB] Get: 85 http://deb.debian.org/debian trixie/main armhf python3-psutil armhf 5.9.8-2 [225 kB] Get: 86 http://deb.debian.org/debian trixie/main armhf python3-pygments all 2.17.2+dfsg-1 [818 kB] Get: 87 http://deb.debian.org/debian trixie/main armhf python3-six all 1.16.0-6 [16.3 kB] Get: 88 http://deb.debian.org/debian trixie/main armhf python3-urllib3 all 1.26.18-2 [116 kB] Get: 89 http://deb.debian.org/debian trixie/main armhf python3-requests all 2.31.0+dfsg-2 [68.7 kB] Get: 90 http://deb.debian.org/debian trixie/main armhf python3-snowballstemmer all 2.2.0-4 [58.0 kB] Get: 91 http://deb.debian.org/debian trixie/main armhf sphinx-common all 7.2.6-6 [702 kB] Get: 92 http://deb.debian.org/debian trixie/main armhf python3-sphinx all 7.2.6-6 [552 kB] Get: 93 http://deb.debian.org/debian trixie/main armhf sphinx-rtd-theme-common all 2.0.0+dfsg-1 [1021 kB] Get: 94 http://deb.debian.org/debian trixie/main armhf python3-sphinxcontrib.jquery all 4.1-5 [7348 B] Get: 95 http://deb.debian.org/debian trixie/main armhf python3-sphinx-rtd-theme all 2.0.0+dfsg-1 [28.3 kB] Get: 96 http://deb.debian.org/debian trixie/main armhf python3-ujson armhf 5.10.0-1 [24.4 kB] Fetched 46.0 MB in 1s (79.3 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package fonts-lato. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 19446 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 ... 19788 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 ... 20780 files and directories currently installed.) Preparing to unpack .../00-python3_3.11.8-1_armhf.deb ... Unpacking python3 (3.11.8-1) ... Selecting previously unselected package libpython3.12-minimal:armhf. Preparing to unpack .../01-libpython3.12-minimal_3.12.3-1_armhf.deb ... Unpacking libpython3.12-minimal:armhf (3.12.3-1) ... Selecting previously unselected package python3.12-minimal. Preparing to unpack .../02-python3.12-minimal_3.12.3-1_armhf.deb ... Unpacking python3.12-minimal (3.12.3-1) ... Selecting previously unselected package sgml-base. Preparing to unpack .../03-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../04-sensible-utils_0.0.22_all.deb ... Unpacking sensible-utils (0.0.22) ... Selecting previously unselected package openssl. Preparing to unpack .../05-openssl_3.2.1-3_armhf.deb ... Unpacking openssl (3.2.1-3) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../06-ca-certificates_20240203_all.deb ... Unpacking ca-certificates (20240203) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../07-libmagic-mgc_1%3a5.45-3_armhf.deb ... Unpacking libmagic-mgc (1:5.45-3) ... Selecting previously unselected package libmagic1t64:armhf. Preparing to unpack .../08-libmagic1t64_1%3a5.45-3_armhf.deb ... Unpacking libmagic1t64:armhf (1:5.45-3) ... Selecting previously unselected package file. Preparing to unpack .../09-file_1%3a5.45-3_armhf.deb ... Unpacking file (1:5.45-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../10-gettext-base_0.21-14+b1_armhf.deb ... Unpacking gettext-base (0.21-14+b1) ... Selecting previously unselected package libuchardet0:armhf. Preparing to unpack .../11-libuchardet0_0.0.8-1+b1_armhf.deb ... Unpacking libuchardet0:armhf (0.0.8-1+b1) ... Selecting previously unselected package groff-base. Preparing to unpack .../12-groff-base_1.23.0-4_armhf.deb ... Unpacking groff-base (1.23.0-4) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../13-bsdextrautils_2.40.1-1_armhf.deb ... Unpacking bsdextrautils (2.40.1-1) ... Selecting previously unselected package libpipeline1:armhf. Preparing to unpack .../14-libpipeline1_1.5.7-2_armhf.deb ... Unpacking libpipeline1:armhf (1.5.7-2) ... Selecting previously unselected package man-db. Preparing to unpack .../15-man-db_2.12.1-1_armhf.deb ... Unpacking man-db (2.12.1-1) ... Selecting previously unselected package m4. Preparing to unpack .../16-m4_1.4.19-4_armhf.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../17-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../18-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../19-automake_1%3a1.16.5-1.3_all.deb ... Unpacking automake (1:1.16.5-1.3) ... Selecting previously unselected package autopoint. Preparing to unpack .../20-autopoint_0.21-14_all.deb ... Unpacking autopoint (0.21-14) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../21-libdebhelper-perl_13.15.3_all.deb ... Unpacking libdebhelper-perl (13.15.3) ... Selecting previously unselected package libtool. Preparing to unpack .../22-libtool_2.4.7-7_all.deb ... Unpacking libtool (2.4.7-7) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../23-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../24-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libparams-util-perl. Preparing to unpack .../25-libparams-util-perl_1.102-3_armhf.deb ... Unpacking libparams-util-perl (1.102-3) ... Selecting previously unselected package libsub-install-perl. Preparing to unpack .../26-libsub-install-perl_0.929-1_all.deb ... Unpacking libsub-install-perl (0.929-1) ... Selecting previously unselected package libdata-optlist-perl. Preparing to unpack .../27-libdata-optlist-perl_0.114-1_all.deb ... Unpacking libdata-optlist-perl (0.114-1) ... Selecting previously unselected package libsub-exporter-perl. Preparing to unpack .../28-libsub-exporter-perl_0.990-1_all.deb ... Unpacking libsub-exporter-perl (0.990-1) ... Selecting previously unselected package libsub-prototype-perl. Preparing to unpack .../29-libsub-prototype-perl_0.03-2+b2_armhf.deb ... Unpacking libsub-prototype-perl (0.03-2+b2) ... Selecting previously unselected package libsub-override-perl. Preparing to unpack .../30-libsub-override-perl_0.11-1_all.deb ... Unpacking libsub-override-perl (0.11-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../31-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 .../32-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 .../33-libelf1t64_0.191-1+b1_armhf.deb ... Unpacking libelf1t64:armhf (0.191-1+b1) ... Selecting previously unselected package dwz. Preparing to unpack .../34-dwz_0.15-1+b2_armhf.deb ... Unpacking dwz (0.15-1+b2) ... Selecting previously unselected package libicu72:armhf. Preparing to unpack .../35-libicu72_72.1-4+b1_armhf.deb ... Unpacking libicu72:armhf (72.1-4+b1) ... Selecting previously unselected package libxml2:armhf. Preparing to unpack .../36-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 .../37-gettext_0.21-14+b1_armhf.deb ... Unpacking gettext (0.21-14+b1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../38-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 .../39-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../40-debhelper_13.15.3_all.deb ... Unpacking debhelper (13.15.3) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../41-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 .../42-python3-lib2to3_3.12.3-1_all.deb ... Unpacking python3-lib2to3 (3.12.3-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../43-python3-distutils_3.12.3-1_all.deb ... Unpacking python3-distutils (3.12.3-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../44-python3-setuptools_68.1.2-2_all.deb ... Unpacking python3-setuptools (68.1.2-2) ... Selecting previously unselected package dh-python. Preparing to unpack .../45-dh-python_6.20240422_all.deb ... Unpacking dh-python (6.20240422) ... Selecting previously unselected package xml-core. Preparing to unpack .../46-xml-core_0.19_all.deb ... Unpacking xml-core (0.19) ... Selecting previously unselected package docutils-common. Preparing to unpack .../47-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 .../48-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 libdouble-conversion3:armhf. Preparing to unpack .../49-libdouble-conversion3_3.3.0-1+b1_armhf.deb ... Unpacking libdouble-conversion3:armhf (3.3.0-1+b1) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../50-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../51-libjs-underscore_1.13.4~dfsg+~1.11.4-3_all.deb ... Unpacking libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../52-libjs-sphinxdoc_7.2.6-6_all.deb ... Unpacking libjs-sphinxdoc (7.2.6-6) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../53-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package libpython3.12-stdlib:armhf. Preparing to unpack .../54-libpython3.12-stdlib_3.12.3-1_armhf.deb ... Unpacking libpython3.12-stdlib:armhf (3.12.3-1) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../55-python-babel-localedata_2.14.0-1_all.deb ... Unpacking python-babel-localedata (2.14.0-1) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../56-python3-alabaster_0.7.12-1_all.deb ... Unpacking python3-alabaster (0.7.12-1) ... Selecting previously unselected package python3.12. Preparing to unpack .../57-python3.12_3.12.3-1_armhf.deb ... Unpacking python3.12 (3.12.3-1) ... Selecting previously unselected package python3-all. Preparing to unpack .../58-python3-all_3.11.8-1_armhf.deb ... Unpacking python3-all (3.11.8-1) ... Selecting previously unselected package python3-babel. Preparing to unpack .../59-python3-babel_2.14.0-1_all.deb ... Unpacking python3-babel (2.14.0-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../60-python3-certifi_2023.11.17-1_all.deb ... Unpacking python3-certifi (2023.11.17-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../61-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 .../62-python3-charset-normalizer_3.3.2-1_all.deb ... Unpacking python3-charset-normalizer (3.3.2-1) ... Selecting previously unselected package python3-defusedxml. Preparing to unpack .../63-python3-defusedxml_0.7.1-2_all.deb ... Unpacking python3-defusedxml (0.7.1-2) ... Selecting previously unselected package python3-roman. Preparing to unpack .../64-python3-roman_3.3-3_all.deb ... Unpacking python3-roman (3.3-3) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../65-python3-docutils_0.20.1+dfsg-3_all.deb ... Unpacking python3-docutils (0.20.1+dfsg-3) ... Selecting previously unselected package python3-idna. Preparing to unpack .../66-python3-idna_3.6-2_all.deb ... Unpacking python3-idna (3.6-2) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../67-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../68-python3-markupsafe_2.1.5-1_armhf.deb ... Unpacking python3-markupsafe (2.1.5-1) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../69-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../70-python3-packaging_24.0-1_all.deb ... Unpacking python3-packaging (24.0-1) ... Selecting previously unselected package python3-psutil. Preparing to unpack .../71-python3-psutil_5.9.8-2_armhf.deb ... Unpacking python3-psutil (5.9.8-2) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../72-python3-pygments_2.17.2+dfsg-1_all.deb ... Unpacking python3-pygments (2.17.2+dfsg-1) ... Selecting previously unselected package python3-six. Preparing to unpack .../73-python3-six_1.16.0-6_all.deb ... Unpacking python3-six (1.16.0-6) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../74-python3-urllib3_1.26.18-2_all.deb ... Unpacking python3-urllib3 (1.26.18-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../75-python3-requests_2.31.0+dfsg-2_all.deb ... Unpacking python3-requests (2.31.0+dfsg-2) ... Selecting previously unselected package python3-snowballstemmer. Preparing to unpack .../76-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../77-sphinx-common_7.2.6-6_all.deb ... Unpacking sphinx-common (7.2.6-6) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../78-python3-sphinx_7.2.6-6_all.deb ... Unpacking python3-sphinx (7.2.6-6) ... Selecting previously unselected package sphinx-rtd-theme-common. Preparing to unpack .../79-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 .../80-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 .../81-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-ujson:armhf. Preparing to unpack .../82-python3-ujson_5.10.0-1_armhf.deb ... Unpacking python3-ujson:armhf (5.10.0-1) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:armhf (1.5.7-2) ... Setting up libdouble-conversion3:armhf (3.3.0-1+b1) ... Setting up fonts-lato (2.015-1) ... Setting up libicu72:armhf (72.1-4+b1) ... Setting up bsdextrautils (2.40.1-1) ... Setting up libmagic-mgc (1:5.45-3) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libdebhelper-perl (13.15.3) ... Setting up libmagic1t64:armhf (1:5.45-3) ... Setting up libpython3.12-minimal:armhf (3.12.3-1) ... Setting up gettext-base (0.21-14+b1) ... Setting up m4 (1.4.19-4) ... Setting up file (1:5.45-3) ... Setting up libsub-install-perl (0.929-1) ... Setting up libelf1t64:armhf (0.191-1+b1) ... Setting up python-babel-localedata (2.14.0-1) ... Setting up tzdata (2024a-4) ... Current default time zone: 'Etc/UTC' Local time is now: Wed May 22 13:27:01 UTC 2024. Universal Time is now: Wed May 22 13:27:01 UTC 2024. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up autotools-dev (20220109.1) ... Setting up autopoint (0.21-14) ... Setting up libparams-util-perl (1.102-3) ... 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 netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up openssl (3.2.1-3) ... Setting up readline-common (8.2-4) ... Setting up libxml2:armhf (2.9.14+dfsg-1.3+b3) ... Setting up fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) ... Setting up sphinx-rtd-theme-common (2.0.0+dfsg-1) ... Setting up libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Setting up automake (1:1.16.5-1.3) ... update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode Setting up python3.12-minimal (3.12.3-1) ... Setting up gettext (0.21-14+b1) ... Setting up libtool (2.4.7-7) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 146 added, 0 removed; done. Setting up libdata-optlist-perl (0.114-1) ... Setting up libjs-sphinxdoc (7.2.6-6) ... Setting up libreadline8t64:armhf (8.2-4) ... Setting up groff-base (1.23.0-4) ... Setting up xml-core (0.19) ... Setting up libsub-exporter-perl (0.990-1) ... Setting up libpython3.12-stdlib:armhf (3.12.3-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up libpython3.11-stdlib:armhf (3.11.9-1) ... Setting up python3.12 (3.12.3-1) ... Setting up libsub-prototype-perl (0.03-2+b2) ... 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 libsub-override-perl (0.11-1) ... Setting up libpython3-stdlib:armhf (3.11.8-1) ... Setting up libfile-stripnondeterminism-perl (1.13.1-1) ... Setting up python3.11 (3.11.9-1) ... Setting up python3 (3.11.8-1) ... Setting up python3-markupsafe (2.1.5-1) ... Setting up python3-ujson:armhf (5.10.0-1) ... Setting up python3-psutil (5.9.8-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-certifi (2023.11.17-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up python3-idna (3.6-2) ... Setting up python3-urllib3 (1.26.18-2) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up python3-lib2to3 (3.12.3-1) ... Setting up python3-imagesize (1.4.1-1) ... Setting up python3-pkg-resources (68.1.2-2) ... Setting up python3-distutils (3.12.3-1) ... python3.12: can't get files for byte-compilation Setting up python3-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-all (3.11.8-1) ... Setting up debhelper (13.15.3) ... Setting up python3-pygments (2.17.2+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-requests (2.31.0+dfsg-2) ... Setting up dh-python (6.20240422) ... Processing triggers for libc-bin (2.38-11) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.20.1+dfsg-3) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.20.1+dfsg-3) ... Setting up python3-sphinx (7.2.6-6) ... Setting up python3-sphinxcontrib.jquery (4.1-5) ... Setting up python3-sphinx-rtd-theme (2.0.0+dfsg-1) ... Processing triggers for ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Writing extended state information... Building tag database... -> Finished parsing the build-deps I: Building the package I: Running cd /build/reproducible-path/glances-4.0.5+dfsg/ && 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 > ../glances_4.0.5+dfsg-1_source.changes dpkg-buildpackage: info: source package glances dpkg-buildpackage: info: source version 4.0.5+dfsg-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Daniel Echeverri dpkg-source --before-build . dpkg-buildpackage: info: host architecture armhf debian/rules clean dh clean --with python3,sphinxdoc --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/build/reproducible-path/glances-4.0.5+dfsg' rm -rf ./Glances.egg-info dh_auto_clean I: pybuild base:311: python3.12 setup.py clean running clean removing '/build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/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/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build' (and everything under it) 'build/bdist.linux-armv7l' does not exist -- can't clean it 'build/scripts-3.11' does not exist -- can't clean it make[1]: Leaving directory '/build/reproducible-path/glances-4.0.5+dfsg' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild debian/rules binary dh binary --with python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config 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/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/event.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/__main__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/logger.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/client.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/web_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/static_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/password.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/thresholds.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/events_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/filter.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/autodiscover.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/secure.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/main.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/stats_server.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/history.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/stats_client_snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/attribute.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/globals.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/programs.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/webserver.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/stats_client.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/actions.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/password_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/outdated.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/timer.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/amps_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/processes.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/cpu_percent.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/stats.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/folder_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/client_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/server.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/config.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/ports_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances copying glances/standalone.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances running egg_info creating Glances.egg-info writing Glances.egg-info/PKG-INFO writing dependency_links to Glances.egg-info/dependency_links.txt writing entry points to Glances.egg-info/entry_points.txt writing requirements to Glances.egg-info/requires.txt writing top-level names to Glances.egg-info/top_level.txt writing manifest file 'Glances.egg-info/SOURCES.txt' reading manifest file 'Glances.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'AUTHORS' writing manifest file 'Glances.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps' to be distributed and are already explicitly excluding 'glances.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.default' to be distributed and are already explicitly excluding 'glances.amps.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.nginx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.nginx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.nginx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.nginx' to be distributed and are already explicitly excluding 'glances.amps.nginx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemd' to be distributed and are already explicitly excluding 'glances.amps.systemd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemv' to be distributed and are already explicitly excluding 'glances.amps.systemv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports' to be distributed and are already explicitly excluding 'glances.exports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_cassandra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_cassandra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_cassandra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_cassandra' to be distributed and are already explicitly excluding 'glances.exports.glances_cassandra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_couchdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_couchdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_couchdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_couchdb' to be distributed and are already explicitly excluding 'glances.exports.glances_couchdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_csv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_csv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_csv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_csv' to be distributed and are already explicitly excluding 'glances.exports.glances_csv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_elasticsearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_elasticsearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_elasticsearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_elasticsearch' to be distributed and are already explicitly excluding 'glances.exports.glances_elasticsearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graph' to be distributed and are already explicitly excluding 'glances.exports.glances_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graphite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graphite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graphite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graphite' to be distributed and are already explicitly excluding 'glances.exports.glances_graphite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb2' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_json' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_json' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_json' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_json' to be distributed and are already explicitly excluding 'glances.exports.glances_json' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_kafka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_kafka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_kafka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_kafka' to be distributed and are already explicitly excluding 'glances.exports.glances_kafka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mongodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mongodb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mongodb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mongodb' to be distributed and are already explicitly excluding 'glances.exports.glances_mongodb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mqtt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mqtt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mqtt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mqtt' to be distributed and are already explicitly excluding 'glances.exports.glances_mqtt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_opentsdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_opentsdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_opentsdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_opentsdb' to be distributed and are already explicitly excluding 'glances.exports.glances_opentsdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_prometheus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_prometheus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_prometheus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_prometheus' to be distributed and are already explicitly excluding 'glances.exports.glances_prometheus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_rabbitmq' to be distributed and are already explicitly excluding 'glances.exports.glances_rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_restful' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_restful' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_restful' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_restful' to be distributed and are already explicitly excluding 'glances.exports.glances_restful' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_riemann' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_riemann' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_riemann' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_riemann' to be distributed and are already explicitly excluding 'glances.exports.glances_riemann' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_statsd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_statsd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_statsd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_statsd' to be distributed and are already explicitly excluding 'glances.exports.glances_statsd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_zeromq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_zeromq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_zeromq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_zeromq' to be distributed and are already explicitly excluding 'glances.exports.glances_zeromq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs' to be distributed and are already explicitly excluding 'glances.outputs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static' to be distributed and are already explicitly excluding 'glances.outputs.static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.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 'glances.outputs.static.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 'glances.outputs.static.css' to be distributed and are already explicitly excluding 'glances.outputs.static.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 'glances.outputs.static.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.images' to be distributed and are already explicitly excluding 'glances.outputs.static.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js' to be distributed and are already explicitly excluding 'glances.outputs.static.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js.components' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js.components' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js.components' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js.components' to be distributed and are already explicitly excluding 'glances.outputs.static.js.components' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.templates' to be distributed and are already explicitly excluding 'glances.outputs.static.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins' to be distributed and are already explicitly excluding 'glances.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.alert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.alert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.alert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.alert' to be distributed and are already explicitly excluding 'glances.plugins.alert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.amps' to be distributed and are already explicitly excluding 'glances.plugins.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cloud' to be distributed and are already explicitly excluding 'glances.plugins.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.connections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.connections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.connections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.connections' to be distributed and are already explicitly excluding 'glances.plugins.connections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers' to be distributed and are already explicitly excluding 'glances.plugins.containers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers.engines' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers.engines' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers.engines' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers.engines' to be distributed and are already explicitly excluding 'glances.plugins.containers.engines' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.core' to be distributed and are already explicitly excluding 'glances.plugins.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cpu' to be distributed and are already explicitly excluding 'glances.plugins.cpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.diskio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.diskio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.diskio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.diskio' to be distributed and are already explicitly excluding 'glances.plugins.diskio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.folders' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.folders' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.folders' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.folders' to be distributed and are already explicitly excluding 'glances.plugins.folders' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.fs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.fs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.fs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.fs' to be distributed and are already explicitly excluding 'glances.plugins.fs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu' to be distributed and are already explicitly excluding 'glances.plugins.gpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu.cards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu.cards' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu.cards' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu.cards' to be distributed and are already explicitly excluding 'glances.plugins.gpu.cards' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.help' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.help' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.help' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.help' to be distributed and are already explicitly excluding 'glances.plugins.help' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ip' to be distributed and are already explicitly excluding 'glances.plugins.ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.irq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.irq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.irq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.irq' to be distributed and are already explicitly excluding 'glances.plugins.irq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.load' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.load' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.load' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.load' to be distributed and are already explicitly excluding 'glances.plugins.load' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.mem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.mem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.mem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.mem' to be distributed and are already explicitly excluding 'glances.plugins.mem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.memswap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.memswap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.memswap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.memswap' to be distributed and are already explicitly excluding 'glances.plugins.memswap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.network' to be distributed and are already explicitly excluding 'glances.plugins.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.now' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.now' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.now' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.now' to be distributed and are already explicitly excluding 'glances.plugins.now' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.percpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.percpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.percpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.percpu' to be distributed and are already explicitly excluding 'glances.plugins.percpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.plugin' to be distributed and are already explicitly excluding 'glances.plugins.plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ports' to be distributed and are already explicitly excluding 'glances.plugins.ports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processcount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processcount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processcount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processcount' to be distributed and are already explicitly excluding 'glances.plugins.processcount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processlist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processlist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processlist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processlist' to be distributed and are already explicitly excluding 'glances.plugins.processlist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.psutilversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.psutilversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.psutilversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.psutilversion' to be distributed and are already explicitly excluding 'glances.plugins.psutilversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.quicklook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.quicklook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.quicklook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.quicklook' to be distributed and are already explicitly excluding 'glances.plugins.quicklook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.raid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.raid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.raid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.raid' to be distributed and are already explicitly excluding 'glances.plugins.raid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors' to be distributed and are already explicitly excluding 'glances.plugins.sensors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors.sensor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors.sensor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors.sensor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors.sensor' to be distributed and are already explicitly excluding 'glances.plugins.sensors.sensor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.smart' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.smart' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.smart' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.smart' to be distributed and are already explicitly excluding 'glances.plugins.smart' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.system' to be distributed and are already explicitly excluding 'glances.plugins.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.uptime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.uptime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.uptime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.uptime' to be distributed and are already explicitly excluding 'glances.plugins.uptime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.version' to be distributed and are already explicitly excluding 'glances.plugins.version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.wifi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.wifi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.wifi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.wifi' to be distributed and are already explicitly excluding 'glances.plugins.wifi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps copying glances/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps copying glances/amps/amp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/default copying glances/amps/default/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/default creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/nginx copying glances/amps/nginx/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/nginx creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/systemd copying glances/amps/systemd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/systemd creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/systemv copying glances/amps/systemv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/systemv creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports copying glances/exports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports copying glances/exports/export.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_cassandra copying glances/exports/glances_cassandra/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_cassandra creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_couchdb copying glances/exports/glances_couchdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_couchdb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_csv copying glances/exports/glances_csv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_csv creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_elasticsearch copying glances/exports/glances_elasticsearch/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_elasticsearch creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_graph copying glances/exports/glances_graph/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_graph creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_graphite copying glances/exports/glances_graphite/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_graphite creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_influxdb copying glances/exports/glances_influxdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_influxdb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_influxdb2 copying glances/exports/glances_influxdb2/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_influxdb2 creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_json copying glances/exports/glances_json/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_json creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_kafka copying glances/exports/glances_kafka/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_kafka creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_mongodb copying glances/exports/glances_mongodb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_mongodb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_mqtt copying glances/exports/glances_mqtt/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_mqtt creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_opentsdb copying glances/exports/glances_opentsdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_opentsdb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_prometheus copying glances/exports/glances_prometheus/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_prometheus creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_rabbitmq copying glances/exports/glances_rabbitmq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_rabbitmq creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_restful copying glances/exports/glances_restful/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_restful creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_riemann copying glances/exports/glances_riemann/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_riemann creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_statsd copying glances/exports/glances_statsd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_statsd creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_zeromq copying glances/exports/glances_zeromq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_zeromq creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_bars.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_curses.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_curses_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_restful_api.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_sparklines.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_stdout.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_stdout_apidoc.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_stdout_csv.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_stdout_issue.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_stdout_json.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs copying glances/outputs/glances_unicode.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static copying glances/outputs/static/.eslintrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static copying glances/outputs/static/.prettierrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static copying glances/outputs/static/README.md -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static copying glances/outputs/static/package-lock.json -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static copying glances/outputs/static/package.json -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static copying glances/outputs/static/webpack.config.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css copying glances/outputs/static/css/bootstrap.less -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css copying glances/outputs/static/css/style.scss -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css copying glances/outputs/static/css/variables.less -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/images copying glances/outputs/static/images/favicon.ico -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/images copying glances/outputs/static/images/glances.png -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/images creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js copying glances/outputs/static/js/App.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js copying glances/outputs/static/js/app.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js copying glances/outputs/static/js/filters.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js copying glances/outputs/static/js/services.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js copying glances/outputs/static/js/store.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js copying glances/outputs/static/js/uiconfig.json -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/help.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-alert.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-amps.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-cloud.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-connections.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-containers.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-cpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-diskio.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-folders.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-fs.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-gpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-ip.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-irq.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-load.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-mem-more.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-mem.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-memswap.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-network.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-now.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-percpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-ports.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-process.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-processcount.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-processlist.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-quicklook.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-raid.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-sensors.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-smart.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-system.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-uptime.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-wifi.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/templates copying glances/outputs/static/templates/index.html -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/templates creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins copying glances/plugins/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/alert copying glances/plugins/alert/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/alert creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/amps copying glances/plugins/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/amps creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/cloud copying glances/plugins/cloud/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/cloud creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/connections copying glances/plugins/connections/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/connections creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers copying glances/plugins/containers/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers copying glances/plugins/containers/stats_streamer.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines copying glances/plugins/containers/engines/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines copying glances/plugins/containers/engines/docker.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines copying glances/plugins/containers/engines/podman.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/core copying glances/plugins/core/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/core creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/cpu copying glances/plugins/cpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/cpu creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/diskio copying glances/plugins/diskio/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/diskio creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/folders copying glances/plugins/folders/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/folders creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/fs copying glances/plugins/fs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/fs creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu copying glances/plugins/gpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/amd.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/nvidia.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/help copying glances/plugins/help/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/help creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/ip copying glances/plugins/ip/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/ip creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/irq copying glances/plugins/irq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/irq creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/load copying glances/plugins/load/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/load creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/mem copying glances/plugins/mem/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/mem creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/memswap copying glances/plugins/memswap/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/memswap creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/network copying glances/plugins/network/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/network creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/now copying glances/plugins/now/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/now creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/percpu copying glances/plugins/percpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/percpu creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/plugin copying glances/plugins/plugin/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/plugin copying glances/plugins/plugin/model.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/plugin creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/ports copying glances/plugins/ports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/ports creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/processcount copying glances/plugins/processcount/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/processcount creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/processlist copying glances/plugins/processlist/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/processlist creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/psutilversion copying glances/plugins/psutilversion/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/psutilversion creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/quicklook copying glances/plugins/quicklook/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/quicklook creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/raid copying glances/plugins/raid/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/raid creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors copying glances/plugins/sensors/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/glances_batpercent.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/glances_hddtemp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/smart copying glances/plugins/smart/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/smart creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/system copying glances/plugins/system/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/system creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/uptime copying glances/plugins/uptime/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/uptime creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/version copying glances/plugins/version/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/version creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/wifi copying glances/plugins/wifi/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/wifi I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/event.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/__main__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/logger.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/client.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/web_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/static_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/password.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/thresholds.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/events_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/filter.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/autodiscover.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/secure.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/main.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/stats_server.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/history.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/stats_client_snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/attribute.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/globals.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/programs.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/webserver.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/stats_client.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/actions.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/password_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/outdated.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/timer.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/amps_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/processes.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/cpu_percent.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/stats.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/folder_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/client_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/server.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/config.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/ports_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances copying glances/standalone.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances running egg_info writing Glances.egg-info/PKG-INFO writing dependency_links to Glances.egg-info/dependency_links.txt writing entry points to Glances.egg-info/entry_points.txt writing requirements to Glances.egg-info/requires.txt writing top-level names to Glances.egg-info/top_level.txt reading manifest file 'Glances.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'AUTHORS' writing manifest file 'Glances.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps' to be distributed and are already explicitly excluding 'glances.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.default' to be distributed and are already explicitly excluding 'glances.amps.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.nginx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.nginx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.nginx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.nginx' to be distributed and are already explicitly excluding 'glances.amps.nginx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemd' to be distributed and are already explicitly excluding 'glances.amps.systemd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemv' to be distributed and are already explicitly excluding 'glances.amps.systemv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports' to be distributed and are already explicitly excluding 'glances.exports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_cassandra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_cassandra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_cassandra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_cassandra' to be distributed and are already explicitly excluding 'glances.exports.glances_cassandra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_couchdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_couchdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_couchdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_couchdb' to be distributed and are already explicitly excluding 'glances.exports.glances_couchdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_csv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_csv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_csv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_csv' to be distributed and are already explicitly excluding 'glances.exports.glances_csv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_elasticsearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_elasticsearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_elasticsearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_elasticsearch' to be distributed and are already explicitly excluding 'glances.exports.glances_elasticsearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graph' to be distributed and are already explicitly excluding 'glances.exports.glances_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graphite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graphite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graphite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graphite' to be distributed and are already explicitly excluding 'glances.exports.glances_graphite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb2' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_json' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_json' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_json' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_json' to be distributed and are already explicitly excluding 'glances.exports.glances_json' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_kafka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_kafka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_kafka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_kafka' to be distributed and are already explicitly excluding 'glances.exports.glances_kafka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mongodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mongodb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mongodb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mongodb' to be distributed and are already explicitly excluding 'glances.exports.glances_mongodb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mqtt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mqtt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mqtt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mqtt' to be distributed and are already explicitly excluding 'glances.exports.glances_mqtt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_opentsdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_opentsdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_opentsdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_opentsdb' to be distributed and are already explicitly excluding 'glances.exports.glances_opentsdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_prometheus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_prometheus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_prometheus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_prometheus' to be distributed and are already explicitly excluding 'glances.exports.glances_prometheus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_rabbitmq' to be distributed and are already explicitly excluding 'glances.exports.glances_rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_restful' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_restful' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_restful' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_restful' to be distributed and are already explicitly excluding 'glances.exports.glances_restful' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_riemann' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_riemann' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_riemann' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_riemann' to be distributed and are already explicitly excluding 'glances.exports.glances_riemann' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_statsd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_statsd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_statsd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_statsd' to be distributed and are already explicitly excluding 'glances.exports.glances_statsd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_zeromq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_zeromq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_zeromq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_zeromq' to be distributed and are already explicitly excluding 'glances.exports.glances_zeromq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs' to be distributed and are already explicitly excluding 'glances.outputs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static' to be distributed and are already explicitly excluding 'glances.outputs.static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.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 'glances.outputs.static.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 'glances.outputs.static.css' to be distributed and are already explicitly excluding 'glances.outputs.static.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 'glances.outputs.static.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.images' to be distributed and are already explicitly excluding 'glances.outputs.static.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js' to be distributed and are already explicitly excluding 'glances.outputs.static.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js.components' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js.components' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js.components' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js.components' to be distributed and are already explicitly excluding 'glances.outputs.static.js.components' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.templates' to be distributed and are already explicitly excluding 'glances.outputs.static.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins' to be distributed and are already explicitly excluding 'glances.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.alert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.alert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.alert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.alert' to be distributed and are already explicitly excluding 'glances.plugins.alert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.amps' to be distributed and are already explicitly excluding 'glances.plugins.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cloud' to be distributed and are already explicitly excluding 'glances.plugins.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.connections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.connections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.connections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.connections' to be distributed and are already explicitly excluding 'glances.plugins.connections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers' to be distributed and are already explicitly excluding 'glances.plugins.containers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers.engines' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers.engines' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers.engines' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers.engines' to be distributed and are already explicitly excluding 'glances.plugins.containers.engines' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.core' to be distributed and are already explicitly excluding 'glances.plugins.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cpu' to be distributed and are already explicitly excluding 'glances.plugins.cpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.diskio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.diskio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.diskio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.diskio' to be distributed and are already explicitly excluding 'glances.plugins.diskio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.folders' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.folders' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.folders' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.folders' to be distributed and are already explicitly excluding 'glances.plugins.folders' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.fs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.fs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.fs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.fs' to be distributed and are already explicitly excluding 'glances.plugins.fs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu' to be distributed and are already explicitly excluding 'glances.plugins.gpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu.cards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu.cards' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu.cards' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu.cards' to be distributed and are already explicitly excluding 'glances.plugins.gpu.cards' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.help' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.help' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.help' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.help' to be distributed and are already explicitly excluding 'glances.plugins.help' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ip' to be distributed and are already explicitly excluding 'glances.plugins.ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.irq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.irq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.irq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.irq' to be distributed and are already explicitly excluding 'glances.plugins.irq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.load' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.load' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.load' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.load' to be distributed and are already explicitly excluding 'glances.plugins.load' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.mem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.mem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.mem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.mem' to be distributed and are already explicitly excluding 'glances.plugins.mem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.memswap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.memswap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.memswap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.memswap' to be distributed and are already explicitly excluding 'glances.plugins.memswap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.network' to be distributed and are already explicitly excluding 'glances.plugins.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.now' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.now' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.now' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.now' to be distributed and are already explicitly excluding 'glances.plugins.now' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.percpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.percpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.percpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.percpu' to be distributed and are already explicitly excluding 'glances.plugins.percpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.plugin' to be distributed and are already explicitly excluding 'glances.plugins.plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ports' to be distributed and are already explicitly excluding 'glances.plugins.ports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processcount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processcount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processcount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processcount' to be distributed and are already explicitly excluding 'glances.plugins.processcount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processlist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processlist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processlist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processlist' to be distributed and are already explicitly excluding 'glances.plugins.processlist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.psutilversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.psutilversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.psutilversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.psutilversion' to be distributed and are already explicitly excluding 'glances.plugins.psutilversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.quicklook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.quicklook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.quicklook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.quicklook' to be distributed and are already explicitly excluding 'glances.plugins.quicklook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.raid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.raid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.raid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.raid' to be distributed and are already explicitly excluding 'glances.plugins.raid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors' to be distributed and are already explicitly excluding 'glances.plugins.sensors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors.sensor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors.sensor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors.sensor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors.sensor' to be distributed and are already explicitly excluding 'glances.plugins.sensors.sensor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.smart' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.smart' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.smart' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.smart' to be distributed and are already explicitly excluding 'glances.plugins.smart' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.system' to be distributed and are already explicitly excluding 'glances.plugins.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.uptime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.uptime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.uptime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.uptime' to be distributed and are already explicitly excluding 'glances.plugins.uptime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.version' to be distributed and are already explicitly excluding 'glances.plugins.version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.wifi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.wifi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.wifi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.wifi' to be distributed and are already explicitly excluding 'glances.plugins.wifi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps copying glances/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps copying glances/amps/amp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/default copying glances/amps/default/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/default creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/nginx copying glances/amps/nginx/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/nginx creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/systemd copying glances/amps/systemd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/systemd creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/systemv copying glances/amps/systemv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/systemv creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports copying glances/exports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports copying glances/exports/export.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_cassandra copying glances/exports/glances_cassandra/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_cassandra creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_couchdb copying glances/exports/glances_couchdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_couchdb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_csv copying glances/exports/glances_csv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_csv creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_elasticsearch copying glances/exports/glances_elasticsearch/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_elasticsearch creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_graph copying glances/exports/glances_graph/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_graph creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_graphite copying glances/exports/glances_graphite/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_graphite creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_influxdb copying glances/exports/glances_influxdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_influxdb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_influxdb2 copying glances/exports/glances_influxdb2/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_influxdb2 creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_json copying glances/exports/glances_json/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_json creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_kafka copying glances/exports/glances_kafka/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_kafka creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_mongodb copying glances/exports/glances_mongodb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_mongodb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_mqtt copying glances/exports/glances_mqtt/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_mqtt creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_opentsdb copying glances/exports/glances_opentsdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_opentsdb creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_prometheus copying glances/exports/glances_prometheus/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_prometheus creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_rabbitmq copying glances/exports/glances_rabbitmq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_rabbitmq creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_restful copying glances/exports/glances_restful/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_restful creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_riemann copying glances/exports/glances_riemann/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_riemann creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_statsd copying glances/exports/glances_statsd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_statsd creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_zeromq copying glances/exports/glances_zeromq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_zeromq creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_bars.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_curses.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_curses_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_restful_api.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_sparklines.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_stdout.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_stdout_apidoc.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_stdout_csv.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_stdout_issue.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_stdout_json.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs copying glances/outputs/glances_unicode.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static copying glances/outputs/static/.eslintrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static copying glances/outputs/static/.prettierrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static copying glances/outputs/static/README.md -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static copying glances/outputs/static/package-lock.json -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static copying glances/outputs/static/package.json -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static copying glances/outputs/static/webpack.config.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css copying glances/outputs/static/css/bootstrap.less -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css copying glances/outputs/static/css/style.scss -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css copying glances/outputs/static/css/variables.less -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/images copying glances/outputs/static/images/favicon.ico -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/images copying glances/outputs/static/images/glances.png -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/images creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js copying glances/outputs/static/js/App.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js copying glances/outputs/static/js/app.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js copying glances/outputs/static/js/filters.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js copying glances/outputs/static/js/services.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js copying glances/outputs/static/js/store.js -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js copying glances/outputs/static/js/uiconfig.json -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/help.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-alert.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-amps.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-cloud.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-connections.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-containers.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-cpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-diskio.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-folders.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-fs.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-gpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-ip.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-irq.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-load.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-mem-more.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-mem.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-memswap.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-network.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-now.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-percpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-ports.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-process.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-processcount.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-processlist.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-quicklook.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-raid.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-sensors.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-smart.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-system.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-uptime.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-wifi.vue -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/templates copying glances/outputs/static/templates/index.html -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/templates creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins copying glances/plugins/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/alert copying glances/plugins/alert/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/alert creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/amps copying glances/plugins/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/amps creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/cloud copying glances/plugins/cloud/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/cloud creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/connections copying glances/plugins/connections/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/connections creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers copying glances/plugins/containers/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers copying glances/plugins/containers/stats_streamer.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines copying glances/plugins/containers/engines/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines copying glances/plugins/containers/engines/docker.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines copying glances/plugins/containers/engines/podman.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/core copying glances/plugins/core/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/core creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/cpu copying glances/plugins/cpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/cpu creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/diskio copying glances/plugins/diskio/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/diskio creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/folders copying glances/plugins/folders/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/folders creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/fs copying glances/plugins/fs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/fs creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu copying glances/plugins/gpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/amd.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/nvidia.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/help copying glances/plugins/help/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/help creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/ip copying glances/plugins/ip/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/ip creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/irq copying glances/plugins/irq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/irq creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/load copying glances/plugins/load/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/load creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/mem copying glances/plugins/mem/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/mem creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/memswap copying glances/plugins/memswap/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/memswap creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/network copying glances/plugins/network/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/network creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/now copying glances/plugins/now/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/now creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/percpu copying glances/plugins/percpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/percpu creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/plugin copying glances/plugins/plugin/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/plugin copying glances/plugins/plugin/model.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/plugin creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/ports copying glances/plugins/ports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/ports creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/processcount copying glances/plugins/processcount/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/processcount creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/processlist copying glances/plugins/processlist/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/processlist creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/psutilversion copying glances/plugins/psutilversion/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/psutilversion creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/quicklook copying glances/plugins/quicklook/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/quicklook creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/raid copying glances/plugins/raid/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/raid creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors copying glances/plugins/sensors/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/glances_batpercent.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/glances_hddtemp.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/smart copying glances/plugins/smart/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/smart creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/system copying glances/plugins/system/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/system creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/uptime copying glances/plugins/uptime/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/uptime creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/version copying glances/plugins/version/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/version creating /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/wifi copying glances/plugins/wifi/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/wifi create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild debian/rules override_dh_auto_install make[1]: Entering directory '/build/reproducible-path/glances-4.0.5+dfsg' dh_auto_install --destdir /build/reproducible-path/glances-4.0.5+dfsg/debian/glances I: pybuild base:311: /usr/bin/python3.12 setup.py install --root /build/reproducible-path/glances-4.0.5+dfsg/debian/glances 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 Glances.egg-info/PKG-INFO writing dependency_links to Glances.egg-info/dependency_links.txt writing entry points to Glances.egg-info/entry_points.txt writing requirements to Glances.egg-info/requires.txt writing top-level names to Glances.egg-info/top_level.txt reading manifest file 'Glances.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'AUTHORS' writing manifest file 'Glances.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps' to be distributed and are already explicitly excluding 'glances.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.default' to be distributed and are already explicitly excluding 'glances.amps.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.nginx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.nginx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.nginx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.nginx' to be distributed and are already explicitly excluding 'glances.amps.nginx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemd' to be distributed and are already explicitly excluding 'glances.amps.systemd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemv' to be distributed and are already explicitly excluding 'glances.amps.systemv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports' to be distributed and are already explicitly excluding 'glances.exports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_cassandra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_cassandra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_cassandra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_cassandra' to be distributed and are already explicitly excluding 'glances.exports.glances_cassandra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_couchdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_couchdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_couchdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_couchdb' to be distributed and are already explicitly excluding 'glances.exports.glances_couchdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_csv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_csv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_csv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_csv' to be distributed and are already explicitly excluding 'glances.exports.glances_csv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_elasticsearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_elasticsearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_elasticsearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_elasticsearch' to be distributed and are already explicitly excluding 'glances.exports.glances_elasticsearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graph' to be distributed and are already explicitly excluding 'glances.exports.glances_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graphite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graphite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graphite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graphite' to be distributed and are already explicitly excluding 'glances.exports.glances_graphite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb2' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_json' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_json' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_json' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_json' to be distributed and are already explicitly excluding 'glances.exports.glances_json' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_kafka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_kafka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_kafka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_kafka' to be distributed and are already explicitly excluding 'glances.exports.glances_kafka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mongodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mongodb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mongodb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mongodb' to be distributed and are already explicitly excluding 'glances.exports.glances_mongodb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mqtt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mqtt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mqtt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mqtt' to be distributed and are already explicitly excluding 'glances.exports.glances_mqtt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_opentsdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_opentsdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_opentsdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_opentsdb' to be distributed and are already explicitly excluding 'glances.exports.glances_opentsdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_prometheus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_prometheus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_prometheus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_prometheus' to be distributed and are already explicitly excluding 'glances.exports.glances_prometheus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_rabbitmq' to be distributed and are already explicitly excluding 'glances.exports.glances_rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_restful' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_restful' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_restful' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_restful' to be distributed and are already explicitly excluding 'glances.exports.glances_restful' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_riemann' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_riemann' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_riemann' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_riemann' to be distributed and are already explicitly excluding 'glances.exports.glances_riemann' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_statsd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_statsd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_statsd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_statsd' to be distributed and are already explicitly excluding 'glances.exports.glances_statsd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_zeromq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_zeromq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_zeromq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_zeromq' to be distributed and are already explicitly excluding 'glances.exports.glances_zeromq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs' to be distributed and are already explicitly excluding 'glances.outputs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static' to be distributed and are already explicitly excluding 'glances.outputs.static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.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 'glances.outputs.static.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 'glances.outputs.static.css' to be distributed and are already explicitly excluding 'glances.outputs.static.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 'glances.outputs.static.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.images' to be distributed and are already explicitly excluding 'glances.outputs.static.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js' to be distributed and are already explicitly excluding 'glances.outputs.static.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js.components' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js.components' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js.components' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js.components' to be distributed and are already explicitly excluding 'glances.outputs.static.js.components' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.templates' to be distributed and are already explicitly excluding 'glances.outputs.static.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins' to be distributed and are already explicitly excluding 'glances.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.alert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.alert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.alert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.alert' to be distributed and are already explicitly excluding 'glances.plugins.alert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.amps' to be distributed and are already explicitly excluding 'glances.plugins.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cloud' to be distributed and are already explicitly excluding 'glances.plugins.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.connections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.connections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.connections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.connections' to be distributed and are already explicitly excluding 'glances.plugins.connections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers' to be distributed and are already explicitly excluding 'glances.plugins.containers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers.engines' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers.engines' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers.engines' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers.engines' to be distributed and are already explicitly excluding 'glances.plugins.containers.engines' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.core' to be distributed and are already explicitly excluding 'glances.plugins.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cpu' to be distributed and are already explicitly excluding 'glances.plugins.cpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.diskio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.diskio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.diskio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.diskio' to be distributed and are already explicitly excluding 'glances.plugins.diskio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.folders' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.folders' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.folders' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.folders' to be distributed and are already explicitly excluding 'glances.plugins.folders' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.fs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.fs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.fs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.fs' to be distributed and are already explicitly excluding 'glances.plugins.fs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu' to be distributed and are already explicitly excluding 'glances.plugins.gpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu.cards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu.cards' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu.cards' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu.cards' to be distributed and are already explicitly excluding 'glances.plugins.gpu.cards' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.help' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.help' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.help' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.help' to be distributed and are already explicitly excluding 'glances.plugins.help' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ip' to be distributed and are already explicitly excluding 'glances.plugins.ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.irq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.irq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.irq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.irq' to be distributed and are already explicitly excluding 'glances.plugins.irq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.load' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.load' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.load' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.load' to be distributed and are already explicitly excluding 'glances.plugins.load' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.mem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.mem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.mem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.mem' to be distributed and are already explicitly excluding 'glances.plugins.mem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.memswap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.memswap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.memswap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.memswap' to be distributed and are already explicitly excluding 'glances.plugins.memswap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.network' to be distributed and are already explicitly excluding 'glances.plugins.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.now' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.now' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.now' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.now' to be distributed and are already explicitly excluding 'glances.plugins.now' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.percpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.percpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.percpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.percpu' to be distributed and are already explicitly excluding 'glances.plugins.percpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.plugin' to be distributed and are already explicitly excluding 'glances.plugins.plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ports' to be distributed and are already explicitly excluding 'glances.plugins.ports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processcount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processcount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processcount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processcount' to be distributed and are already explicitly excluding 'glances.plugins.processcount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processlist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processlist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processlist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processlist' to be distributed and are already explicitly excluding 'glances.plugins.processlist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.psutilversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.psutilversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.psutilversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.psutilversion' to be distributed and are already explicitly excluding 'glances.plugins.psutilversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.quicklook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.quicklook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.quicklook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.quicklook' to be distributed and are already explicitly excluding 'glances.plugins.quicklook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.raid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.raid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.raid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.raid' to be distributed and are already explicitly excluding 'glances.plugins.raid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors' to be distributed and are already explicitly excluding 'glances.plugins.sensors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors.sensor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors.sensor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors.sensor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors.sensor' to be distributed and are already explicitly excluding 'glances.plugins.sensors.sensor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.smart' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.smart' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.smart' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.smart' to be distributed and are already explicitly excluding 'glances.plugins.smart' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.system' to be distributed and are already explicitly excluding 'glances.plugins.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.uptime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.uptime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.uptime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.uptime' to be distributed and are already explicitly excluding 'glances.plugins.uptime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.version' to be distributed and are already explicitly excluding 'glances.plugins.version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.wifi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.wifi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.wifi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.wifi' to be distributed and are already explicitly excluding 'glances.plugins.wifi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/glances-4.0.5+dfsg/debian/glances/usr creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12 creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/event.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/__main__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/logger.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/client.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/web_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/static_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/password.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/thresholds.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/events_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/filter.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/autodiscover.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/secure.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/main.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/stats_server.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/history.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/stats_client_snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/attribute.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/globals.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/programs.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/webserver.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/stats_client.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/actions.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/password_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_bars.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_stdout.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_curses.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/images copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/images/favicon.ico -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/images copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/images/glances.png -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/images copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/.prettierrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/.eslintrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/services.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/filters.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/store.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/uiconfig.json -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/App.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-memswap.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-wifi.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-irq.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-processlist.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-cloud.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-now.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-containers.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-connections.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-quicklook.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-cpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-folders.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-gpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-fs.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-uptime.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/help.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-load.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-ports.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-mem-more.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-mem.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-sensors.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-network.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-percpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-processcount.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-amps.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-diskio.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-ip.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-raid.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-system.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-process.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-smart.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/components/plugin-alert.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/js/app.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/README.md -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css/variables.less -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css/bootstrap.less -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/css/style.scss -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/package.json -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/templates copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/templates/index.html -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static/templates copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/webpack.config.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/static/package-lock.json -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/static copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_curses_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_restful_api.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_unicode.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_sparklines.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_stdout_issue.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_stdout_apidoc.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_stdout_csv.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outputs/glances_stdout_json.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/outdated.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/timer.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/amp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/systemv copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/systemv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/systemv creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/default copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/default/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/default creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/systemd copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/systemd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/systemd creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/nginx copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/nginx/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/nginx copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/amps_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/processes.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/cpu_percent.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/stats.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/folder_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/client_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/load copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/load/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/load creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/smart copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/smart/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/smart creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/ports copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/ports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/ports creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/percpu copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/percpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/percpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/core copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/core/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/core creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/system copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/system/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/system creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/quicklook copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/quicklook/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/quicklook creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/irq copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/irq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/irq creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/alert copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/alert/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/alert creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/uptime copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/uptime/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/uptime creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/processcount copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/processcount/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/processcount creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/wifi copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/wifi/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/wifi creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/fs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/fs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/fs creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/help copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/help/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/help creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/mem copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/mem/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/mem creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards/nvidia.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/cards/amd.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/gpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/version copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/version/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/version creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/cpu copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/cpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/cpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/stats_streamer.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines/podman.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/engines/docker.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/containers/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/amps copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/amps creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/psutilversion copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/psutilversion/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/psutilversion creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/memswap copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/memswap/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/memswap creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/processlist copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/processlist/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/processlist creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/diskio copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/diskio/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/diskio creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/now copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/now/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/now creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/ip copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/ip/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/ip creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/raid copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/raid/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/raid creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/network copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/network/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/network creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor/glances_hddtemp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor/glances_batpercent.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/sensors/sensor/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/folders copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/folders/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/folders creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/plugin copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/plugin/model.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/plugin copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/plugin/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/plugin creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/cloud copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/cloud/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/cloud copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/connections copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/plugins/connections/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/connections copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/server.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/config.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/ports_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/standalone.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_mongodb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_mongodb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_mongodb creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_riemann copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_riemann/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_riemann creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_graph copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_graph/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_graph creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_prometheus copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_prometheus/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_prometheus creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_kafka copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_kafka/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_kafka creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_graphite copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_graphite/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_graphite creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_restful copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_restful/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_restful creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_statsd copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_statsd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_statsd creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_rabbitmq copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_rabbitmq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_rabbitmq creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_zeromq copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_zeromq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_zeromq creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_json copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_json/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_json creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_csv copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_csv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_csv creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_opentsdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_opentsdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_opentsdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/export.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_couchdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_couchdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_couchdb creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_mqtt copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_mqtt/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_mqtt creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_cassandra copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_cassandra/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_cassandra creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_influxdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_influxdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_influxdb creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_influxdb2 copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_influxdb2/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_influxdb2 creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_elasticsearch copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.12_glances/build/glances/exports/glances_elasticsearch/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_elasticsearch byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/event.py to event.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/__main__.py to __main__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/logger.py to logger.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/client.py to client.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/web_list.py to web_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/static_list.py to static_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/password.py to password.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/thresholds.py to thresholds.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/events_list.py to events_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/filter.py to filter.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/autodiscover.py to autodiscover.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/secure.py to secure.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/main.py to main.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/stats_server.py to stats_server.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/history.py to history.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/stats_client_snmp.py to stats_client_snmp.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/attribute.py to attribute.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/globals.py to globals.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/programs.py to programs.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/webserver.py to webserver.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/stats_client.py to stats_client.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/actions.py to actions.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/password_list.py to password_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_bars.py to glances_bars.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_stdout.py to glances_stdout.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_curses.py to glances_curses.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_curses_browser.py to glances_curses_browser.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_restful_api.py to glances_restful_api.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_unicode.py to glances_unicode.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_sparklines.py to glances_sparklines.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_stdout_issue.py to glances_stdout_issue.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_stdout_apidoc.py to glances_stdout_apidoc.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_stdout_csv.py to glances_stdout_csv.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outputs/glances_stdout_json.py to glances_stdout_json.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/outdated.py to outdated.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/timer.py to timer.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/amp.py to amp.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/systemv/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/default/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/systemd/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/nginx/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/amps_list.py to amps_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/processes.py to processes.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/cpu_percent.py to cpu_percent.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/stats.py to stats.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/folder_list.py to folder_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/client_browser.py to client_browser.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/load/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/smart/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/ports/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/percpu/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/core/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/system/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/quicklook/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/irq/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/alert/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/uptime/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/processcount/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/wifi/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/fs/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/help/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/mem/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards/nvidia.py to nvidia.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/cards/amd.py to amd.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/gpu/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/version/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/cpu/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/stats_streamer.py to stats_streamer.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines/podman.py to podman.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/engines/docker.py to docker.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/containers/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/amps/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/psutilversion/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/memswap/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/processlist/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/diskio/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/now/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/ip/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/raid/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/network/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor/glances_hddtemp.py to glances_hddtemp.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor/glances_batpercent.py to glances_batpercent.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/sensors/sensor/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/folders/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/plugin/model.py to model.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/plugin/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/cloud/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/plugins/connections/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/server.py to server.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/config.py to config.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/snmp.py to snmp.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/ports_list.py to ports_list.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/standalone.py to standalone.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_mongodb/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_riemann/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_graph/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_prometheus/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_kafka/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_graphite/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_restful/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_statsd/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_rabbitmq/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_zeromq/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_json/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_csv/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_opentsdb/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/export.py to export.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_couchdb/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_mqtt/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_cassandra/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_influxdb/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_influxdb2/__init__.py to __init__.cpython-312.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/glances/exports/glances_elasticsearch/__init__.py to __init__.cpython-312.pyc running install_data creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying AUTHORS -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying COPYING -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying NEWS.rst -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying README.rst -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying SECURITY.md -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying CONTRIBUTING.md -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying conf/glances.conf -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/man creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/man/man1 copying docs/man/glances.1 -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/man/man1 running install_egg_info Copying Glances.egg-info to /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.12/dist-packages/Glances-4.0.5.egg-info Skipping SOURCES.txt running install_scripts Installing glances script to /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/bin I: pybuild base:311: /usr/bin/python3 setup.py install --root /build/reproducible-path/glances-4.0.5+dfsg/debian/glances 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 Glances.egg-info/PKG-INFO writing dependency_links to Glances.egg-info/dependency_links.txt writing entry points to Glances.egg-info/entry_points.txt writing requirements to Glances.egg-info/requires.txt writing top-level names to Glances.egg-info/top_level.txt reading manifest file 'Glances.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'AUTHORS' writing manifest file 'Glances.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps' to be distributed and are already explicitly excluding 'glances.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.default' to be distributed and are already explicitly excluding 'glances.amps.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.nginx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.nginx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.nginx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.nginx' to be distributed and are already explicitly excluding 'glances.amps.nginx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemd' to be distributed and are already explicitly excluding 'glances.amps.systemd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.amps.systemv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.amps.systemv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.amps.systemv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.amps.systemv' to be distributed and are already explicitly excluding 'glances.amps.systemv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports' to be distributed and are already explicitly excluding 'glances.exports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_cassandra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_cassandra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_cassandra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_cassandra' to be distributed and are already explicitly excluding 'glances.exports.glances_cassandra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_couchdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_couchdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_couchdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_couchdb' to be distributed and are already explicitly excluding 'glances.exports.glances_couchdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_csv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_csv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_csv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_csv' to be distributed and are already explicitly excluding 'glances.exports.glances_csv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_elasticsearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_elasticsearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_elasticsearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_elasticsearch' to be distributed and are already explicitly excluding 'glances.exports.glances_elasticsearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graph' to be distributed and are already explicitly excluding 'glances.exports.glances_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_graphite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_graphite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_graphite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_graphite' to be distributed and are already explicitly excluding 'glances.exports.glances_graphite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_influxdb2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_influxdb2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_influxdb2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_influxdb2' to be distributed and are already explicitly excluding 'glances.exports.glances_influxdb2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_json' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_json' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_json' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_json' to be distributed and are already explicitly excluding 'glances.exports.glances_json' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_kafka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_kafka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_kafka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_kafka' to be distributed and are already explicitly excluding 'glances.exports.glances_kafka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mongodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mongodb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mongodb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mongodb' to be distributed and are already explicitly excluding 'glances.exports.glances_mongodb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_mqtt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_mqtt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_mqtt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_mqtt' to be distributed and are already explicitly excluding 'glances.exports.glances_mqtt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_opentsdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_opentsdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_opentsdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_opentsdb' to be distributed and are already explicitly excluding 'glances.exports.glances_opentsdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_prometheus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_prometheus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_prometheus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_prometheus' to be distributed and are already explicitly excluding 'glances.exports.glances_prometheus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_rabbitmq' to be distributed and are already explicitly excluding 'glances.exports.glances_rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_restful' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_restful' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_restful' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_restful' to be distributed and are already explicitly excluding 'glances.exports.glances_restful' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_riemann' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_riemann' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_riemann' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_riemann' to be distributed and are already explicitly excluding 'glances.exports.glances_riemann' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_statsd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_statsd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_statsd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_statsd' to be distributed and are already explicitly excluding 'glances.exports.glances_statsd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.exports.glances_zeromq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.exports.glances_zeromq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.exports.glances_zeromq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.exports.glances_zeromq' to be distributed and are already explicitly excluding 'glances.exports.glances_zeromq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs' to be distributed and are already explicitly excluding 'glances.outputs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static' to be distributed and are already explicitly excluding 'glances.outputs.static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.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 'glances.outputs.static.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 'glances.outputs.static.css' to be distributed and are already explicitly excluding 'glances.outputs.static.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 'glances.outputs.static.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.images' to be distributed and are already explicitly excluding 'glances.outputs.static.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js' to be distributed and are already explicitly excluding 'glances.outputs.static.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.js.components' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.js.components' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.js.components' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.js.components' to be distributed and are already explicitly excluding 'glances.outputs.static.js.components' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.outputs.static.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.outputs.static.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.outputs.static.templates' to be distributed and are already explicitly excluding 'glances.outputs.static.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins' to be distributed and are already explicitly excluding 'glances.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.alert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.alert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.alert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.alert' to be distributed and are already explicitly excluding 'glances.plugins.alert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.amps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.amps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.amps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.amps' to be distributed and are already explicitly excluding 'glances.plugins.amps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cloud' to be distributed and are already explicitly excluding 'glances.plugins.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.connections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.connections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.connections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.connections' to be distributed and are already explicitly excluding 'glances.plugins.connections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers' to be distributed and are already explicitly excluding 'glances.plugins.containers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.containers.engines' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.containers.engines' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.containers.engines' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.containers.engines' to be distributed and are already explicitly excluding 'glances.plugins.containers.engines' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.core' to be distributed and are already explicitly excluding 'glances.plugins.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.cpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.cpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.cpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.cpu' to be distributed and are already explicitly excluding 'glances.plugins.cpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.diskio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.diskio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.diskio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.diskio' to be distributed and are already explicitly excluding 'glances.plugins.diskio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.folders' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.folders' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.folders' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.folders' to be distributed and are already explicitly excluding 'glances.plugins.folders' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.fs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.fs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.fs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.fs' to be distributed and are already explicitly excluding 'glances.plugins.fs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu' to be distributed and are already explicitly excluding 'glances.plugins.gpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.gpu.cards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.gpu.cards' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.gpu.cards' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.gpu.cards' to be distributed and are already explicitly excluding 'glances.plugins.gpu.cards' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.help' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.help' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.help' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.help' to be distributed and are already explicitly excluding 'glances.plugins.help' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ip' to be distributed and are already explicitly excluding 'glances.plugins.ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.irq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.irq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.irq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.irq' to be distributed and are already explicitly excluding 'glances.plugins.irq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.load' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.load' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.load' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.load' to be distributed and are already explicitly excluding 'glances.plugins.load' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.mem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.mem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.mem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.mem' to be distributed and are already explicitly excluding 'glances.plugins.mem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.memswap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.memswap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.memswap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.memswap' to be distributed and are already explicitly excluding 'glances.plugins.memswap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.network' to be distributed and are already explicitly excluding 'glances.plugins.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.now' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.now' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.now' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.now' to be distributed and are already explicitly excluding 'glances.plugins.now' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.percpu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.percpu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.percpu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.percpu' to be distributed and are already explicitly excluding 'glances.plugins.percpu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.plugin' to be distributed and are already explicitly excluding 'glances.plugins.plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.ports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.ports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.ports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.ports' to be distributed and are already explicitly excluding 'glances.plugins.ports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processcount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processcount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processcount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processcount' to be distributed and are already explicitly excluding 'glances.plugins.processcount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.processlist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.processlist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.processlist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.processlist' to be distributed and are already explicitly excluding 'glances.plugins.processlist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.psutilversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.psutilversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.psutilversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.psutilversion' to be distributed and are already explicitly excluding 'glances.plugins.psutilversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.quicklook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.quicklook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.quicklook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.quicklook' to be distributed and are already explicitly excluding 'glances.plugins.quicklook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.raid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.raid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.raid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.raid' to be distributed and are already explicitly excluding 'glances.plugins.raid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors' to be distributed and are already explicitly excluding 'glances.plugins.sensors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.sensors.sensor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.sensors.sensor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.sensors.sensor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.sensors.sensor' to be distributed and are already explicitly excluding 'glances.plugins.sensors.sensor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.smart' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.smart' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.smart' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.smart' to be distributed and are already explicitly excluding 'glances.plugins.smart' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.system' to be distributed and are already explicitly excluding 'glances.plugins.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.uptime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.uptime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.uptime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.uptime' to be distributed and are already explicitly excluding 'glances.plugins.uptime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.version' to be distributed and are already explicitly excluding 'glances.plugins.version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'glances.plugins.wifi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.wifi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.wifi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.wifi' to be distributed and are already explicitly excluding 'glances.plugins.wifi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11 creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/event.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/__main__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/logger.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/client.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/web_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/static_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/password.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/thresholds.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/events_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/filter.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/autodiscover.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/secure.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/main.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/stats_server.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/history.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/stats_client_snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/attribute.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/globals.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/programs.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/webserver.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/stats_client.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/actions.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/password_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_bars.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_stdout.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_curses.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/images copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/images/favicon.ico -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/images copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/images/glances.png -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/images copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/.prettierrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/.eslintrc.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/services.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/filters.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/store.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/uiconfig.json -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/App.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-memswap.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-wifi.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-irq.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-processlist.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-cloud.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-now.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-containers.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-connections.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-quicklook.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-cpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-folders.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-gpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-fs.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-uptime.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/help.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-load.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-ports.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-mem-more.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-mem.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-sensors.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-network.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-percpu.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-processcount.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-amps.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-diskio.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-ip.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-raid.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-system.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-process.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-smart.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/components/plugin-alert.vue -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js/components copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/js/app.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/js copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/README.md -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css/variables.less -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css/bootstrap.less -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/css/style.scss -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/css copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/package.json -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/templates copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/templates/index.html -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static/templates copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/webpack.config.js -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/static/package-lock.json -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/static copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_curses_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_restful_api.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_unicode.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_sparklines.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_stdout_issue.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_stdout_apidoc.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_stdout_csv.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outputs/glances_stdout_json.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/outdated.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/timer.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/amp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/systemv copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/systemv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/systemv creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/default copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/default/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/default creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/systemd copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/systemd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/systemd creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/nginx copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/nginx/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/nginx copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/amps_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/processes.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/cpu_percent.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/stats.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/folder_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/client_browser.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/load copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/load/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/load creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/smart copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/smart/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/smart creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/ports copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/ports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/ports creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/percpu copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/percpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/percpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/core copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/core/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/core creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/system copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/system/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/system creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/quicklook copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/quicklook/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/quicklook creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/irq copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/irq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/irq creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/alert copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/alert/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/alert creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/uptime copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/uptime/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/uptime creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/processcount copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/processcount/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/processcount creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/wifi copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/wifi/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/wifi creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/fs copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/fs/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/fs creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/help copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/help/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/help creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/mem copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/mem/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/mem creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards/nvidia.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/cards/amd.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/gpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/version copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/version/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/version creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/cpu copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/cpu/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/cpu creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/stats_streamer.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines/podman.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/engines/docker.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/containers/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/amps copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/amps/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/amps creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/psutilversion copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/psutilversion/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/psutilversion creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/memswap copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/memswap/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/memswap creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/processlist copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/processlist/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/processlist creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/diskio copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/diskio/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/diskio creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/now copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/now/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/now creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/ip copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/ip/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/ip creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/raid copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/raid/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/raid creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/network copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/network/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/network creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor/glances_hddtemp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor/glances_batpercent.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/sensors/sensor/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/folders copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/folders/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/folders creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/plugin copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/plugin/model.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/plugin copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/plugin/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/plugin creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/cloud copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/cloud/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/cloud copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/connections copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/plugins/connections/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/connections copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/server.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/config.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/snmp.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/ports_list.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/standalone.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_mongodb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_mongodb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_mongodb creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_riemann copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_riemann/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_riemann creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_graph copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_graph/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_graph creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_prometheus copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_prometheus/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_prometheus creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_kafka copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_kafka/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_kafka creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_graphite copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_graphite/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_graphite creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_restful copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_restful/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_restful creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_statsd copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_statsd/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_statsd creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_rabbitmq copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_rabbitmq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_rabbitmq creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_zeromq copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_zeromq/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_zeromq creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_json copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_json/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_json creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_csv copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_csv/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_csv creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_opentsdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_opentsdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_opentsdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/export.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_couchdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_couchdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_couchdb creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_mqtt copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_mqtt/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_mqtt creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_cassandra copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_cassandra/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_cassandra creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_influxdb copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_influxdb/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_influxdb creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_influxdb2 copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_influxdb2/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_influxdb2 creating /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_elasticsearch copying /build/reproducible-path/glances-4.0.5+dfsg/.pybuild/cpython3_3.11_glances/build/glances/exports/glances_elasticsearch/__init__.py -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_elasticsearch byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/event.py to event.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/__main__.py to __main__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/logger.py to logger.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/client.py to client.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/web_list.py to web_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/static_list.py to static_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/password.py to password.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/thresholds.py to thresholds.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/events_list.py to events_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/filter.py to filter.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/autodiscover.py to autodiscover.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/secure.py to secure.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/main.py to main.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/stats_server.py to stats_server.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/history.py to history.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/stats_client_snmp.py to stats_client_snmp.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/attribute.py to attribute.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/globals.py to globals.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/programs.py to programs.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/webserver.py to webserver.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/stats_client.py to stats_client.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/actions.py to actions.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/password_list.py to password_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_bars.py to glances_bars.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_stdout.py to glances_stdout.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_curses.py to glances_curses.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_curses_browser.py to glances_curses_browser.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_restful_api.py to glances_restful_api.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_unicode.py to glances_unicode.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_sparklines.py to glances_sparklines.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_stdout_issue.py to glances_stdout_issue.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_stdout_apidoc.py to glances_stdout_apidoc.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_stdout_csv.py to glances_stdout_csv.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outputs/glances_stdout_json.py to glances_stdout_json.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/outdated.py to outdated.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/timer.py to timer.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/amp.py to amp.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/systemv/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/default/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/systemd/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/nginx/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/amps_list.py to amps_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/processes.py to processes.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/cpu_percent.py to cpu_percent.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/stats.py to stats.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/folder_list.py to folder_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/client_browser.py to client_browser.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/load/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/smart/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/ports/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/percpu/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/core/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/system/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/quicklook/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/irq/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/alert/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/uptime/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/processcount/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/wifi/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/fs/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/help/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/mem/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards/nvidia.py to nvidia.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/cards/amd.py to amd.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/gpu/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/version/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/cpu/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/stats_streamer.py to stats_streamer.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines/podman.py to podman.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/engines/docker.py to docker.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/containers/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/amps/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/psutilversion/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/memswap/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/processlist/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/diskio/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/now/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/ip/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/raid/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/network/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor/glances_hddtemp.py to glances_hddtemp.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor/glances_batpercent.py to glances_batpercent.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/sensors/sensor/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/folders/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/plugin/model.py to model.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/plugin/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/cloud/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/plugins/connections/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/server.py to server.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/config.py to config.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/snmp.py to snmp.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/ports_list.py to ports_list.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/standalone.py to standalone.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_mongodb/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_riemann/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_graph/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_prometheus/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_kafka/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_graphite/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_restful/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_statsd/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_rabbitmq/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_zeromq/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_json/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_csv/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_opentsdb/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/export.py to export.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_couchdb/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_mqtt/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_cassandra/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_influxdb/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_influxdb2/__init__.py to __init__.cpython-311.pyc byte-compiling /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/glances/exports/glances_elasticsearch/__init__.py to __init__.cpython-311.pyc running install_data copying AUTHORS -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying COPYING -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying NEWS.rst -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying README.rst -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying SECURITY.md -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying CONTRIBUTING.md -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying conf/glances.conf -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances copying docs/man/glances.1 -> /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/man/man1 running install_egg_info Copying Glances.egg-info to /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3.11/dist-packages/Glances-4.0.5.egg-info Skipping SOURCES.txt running install_scripts Installing glances script to /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/bin rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/jquery.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/underscore.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/doctools.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/language_data.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/searchtools.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/js/html5shiv-printshiv.min.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/html/_static/js/html5shiv.min.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3/dist-packages/glances/outputs/static/public/images/glances.png rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python3/dist-packages/glances/outputs/static/images/glances.png rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python*/dist-packages/glances/outputs/static/README.md rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python*/dist-packages/glances/outputs/static/.eslintrc.js rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/lib/python*/dist-packages/glances/outputs/static/.gitignore make[1]: Leaving directory '/build/reproducible-path/glances-4.0.5+dfsg' dh_install -O--buildsystem=pybuild debian/rules override_dh_installdocs make[1]: Entering directory '/build/reproducible-path/glances-4.0.5+dfsg' set -e && for docs in COPYING AUTHORS NEWS glances.conf; do \ rm -f /build/reproducible-path/glances-4.0.5+dfsg/debian/glances/usr/share/doc/glances/$docs ; \ done dh_installdocs make[1]: Leaving directory '/build/reproducible-path/glances-4.0.5+dfsg' debian/rules override_dh_sphinxdoc make[1]: Entering directory '/build/reproducible-path/glances-4.0.5+dfsg' python3 -m sphinx -b html -d debian/tmp/doctrees docs \ debian/glances-doc/usr/share/doc/glances/html Running Sphinx v7.2.6 building [mo]: targets for 0 po files that are out of date building [html]: targets for 54 source files that are out of date updating environment: [new config] 54 added, 0 changed, 0 removed looking for now-outdated files... none found genindex search # Fonts rm -rf /build/reproducible-path/glances-4.0.5+dfsg/debian/glances-doc/usr/share/doc/glances/html/_static/fonts/Lato-* rm -rf /build/reproducible-path/glances-4.0.5+dfsg/debian/glances-doc/usr/share/doc/glances/html/_static/fonts/RobotoSlab-* rm -rf /build/reproducible-path/glances-4.0.5+dfsg/debian/glances-doc/usr/share/doc/glances/html/_static/fonts/fontawesome-* make[1]: Leaving directory '/build/reproducible-path/glances-4.0.5+dfsg' dh_installchangelogs -O--buildsystem=pybuild dh_installman -O--buildsystem=pybuild dh_python3 -O--buildsystem=pybuild dh_installinit -O--buildsystem=pybuild dh_installsystemd -O--buildsystem=pybuild dh_installsystemduser -O--buildsystem=pybuild dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild dh_compress -O--buildsystem=pybuild dh_fixperms -O--buildsystem=pybuild debian/rules override_dh_missing make[1]: Entering directory '/build/reproducible-path/glances-4.0.5+dfsg' rm -rf debian/tmp/doctrees dh_missing --fail-missing make[1]: Leaving directory '/build/reproducible-path/glances-4.0.5+dfsg' dh_installdeb -O--buildsystem=pybuild dh_gencontrol -O--buildsystem=pybuild dpkg-gencontrol: warning: Depends field of package glances-doc: substitution variable ${sphinxdoc:Depends} used, but is not defined dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'glances' in '../glances_4.0.5+dfsg-1_all.deb'. dpkg-deb: building package 'glances-doc' in '../glances-doc_4.0.5+dfsg-1_all.deb'. dpkg-genbuildinfo --build=binary -O../glances_4.0.5+dfsg-1_armhf.buildinfo dpkg-genchanges --build=binary -O../glances_4.0.5+dfsg-1_armhf.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: including full source code in upload I: copying local configuration I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /srv/workspace/pbuilder/4063 and its subdirectories I: Current time: Wed May 22 01:28:25 -12 2024 I: pbuilder-time-stamp: 1716384505 Wed May 22 13:28:48 UTC 2024 I: 1st build successful. Starting 2nd build on remote node ff64a-armhf-rb.debian.net. Wed May 22 13:28:48 UTC 2024 I: Preparing to do remote build '2' on ff64a-armhf-rb.debian.net. Wed May 22 13:53:04 UTC 2024 I: Deleting $TMPDIR on ff64a-armhf-rb.debian.net. Wed May 22 13:53:07 UTC 2024 I: glances_4.0.5+dfsg-1_armhf.changes: Format: 1.8 Date: Sat, 18 May 2024 22:23:48 -0500 Source: glances Binary: glances glances-doc Architecture: all Version: 4.0.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Daniel Echeverri Changed-By: Daniel Echeverri Description: glances - Curses-based monitoring tool glances-doc - Documentation for glances Curses-based monitoring tool Changes: glances (4.0.5+dfsg-1) unstable; urgency=medium . * New upstream release. * debian/control + Bump to Standards-Version 4.7.0 (no changes needed). + Add python-fastapi, python3-uvicorn, python3-jinja2 in Recommends field, and remove python3-bottle * debian/patches + Remove patch 007_disable_ip_module_by_default.diff + merge with upstream. + Refresh others patches. * Update d/copyright file. * Add lintian override to exclude lintian warning. Checksums-Sha1: 8b496f159e380a5f45c3da4ed037536aacc4897e 3086556 glances-doc_4.0.5+dfsg-1_all.deb 51d1a9bd24d9cf8e4671c98d4b9edc534dd76b1e 324576 glances_4.0.5+dfsg-1_all.deb 19aa5984529b6ec071f2dac4e7dbca904eea429f 7164 glances_4.0.5+dfsg-1_armhf.buildinfo Checksums-Sha256: c86aa296b14501e49c7d28667a4c526a6a4c0bb997275c4ae7efa9b3a56416b3 3086556 glances-doc_4.0.5+dfsg-1_all.deb 01d71f66567e758d9782aae968fb8efa767e6990f2ba22548e10316acbb7874e 324576 glances_4.0.5+dfsg-1_all.deb c12d819a1876480bc6e84c44a0c726ad627c0c06f60bb0ae20e8e6ec1fe06baa 7164 glances_4.0.5+dfsg-1_armhf.buildinfo Files: a17f423286fdb4ba7b681da7ed730a90 3086556 doc optional glances-doc_4.0.5+dfsg-1_all.deb 42021620c714996cbac32954047e1594 324576 utils optional glances_4.0.5+dfsg-1_all.deb a1a12f9d6413ea002095df1798efeaa0 7164 utils optional glances_4.0.5+dfsg-1_armhf.buildinfo Wed May 22 13:53:08 UTC 2024 I: diffoscope 266 will be used to compare the two builds: Running as unit: rb-diffoscope-armhf_14-4824.service # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.pChifE4P/glances_4.0.5+dfsg-1.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.pChifE4P/glances_4.0.5+dfsg-1.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.pChifE4P/glances_4.0.5+dfsg-1.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.pChifE4P/b1/glances_4.0.5+dfsg-1_armhf.changes /srv/reproducible-results/rbuild-debian/r-b-build.pChifE4P/b2/glances_4.0.5+dfsg-1_armhf.changes ## command (total time: 0.000s) 0.000s 1 call cmp (internal) ## has_same_content_as (total time: 0.000s) 0.000s 1 call abc.DotChangesFile ## main (total time: 0.404s) 0.404s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.053s) 0.053s 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: 797ms CPU time consumed: 796ms Wed May 22 13:53:13 UTC 2024 I: diffoscope 266 found no differences in the changes files, and a .buildinfo file also exists. Wed May 22 13:53:13 UTC 2024 I: glances from trixie built successfully and reproducibly on armhf. Wed May 22 13:53:15 UTC 2024 I: Submitting .buildinfo files to external archives: Wed May 22 13:53:15 UTC 2024 I: Submitting 8.0K b1/glances_4.0.5+dfsg-1_armhf.buildinfo.asc Wed May 22 13:53:16 UTC 2024 I: Submitting 8.0K b2/glances_4.0.5+dfsg-1_armhf.buildinfo.asc Wed May 22 13:53:17 UTC 2024 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Wed May 22 13:53:17 UTC 2024 I: Done submitting .buildinfo files. Wed May 22 13:53:17 UTC 2024 I: Removing signed glances_4.0.5+dfsg-1_armhf.buildinfo.asc files: removed './b1/glances_4.0.5+dfsg-1_armhf.buildinfo.asc' removed './b2/glances_4.0.5+dfsg-1_armhf.buildinfo.asc'