D: [iurt_root_command] chroot Building target platforms: noarch Building for target noarch Installing /home/pterjan/rpmbuild/SRPMS/glances-4.0.7-2.mga10.src.rpm Executing(%mkbuilddir): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.MaB05z Executing(%prep): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.QuKZhN + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + rm -rf glances-4.0.7 + /usr/lib/rpm/rpmuncompress -x /home/pterjan/rpmbuild/SOURCES/glances-4.0.7.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd glances-4.0.7 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /home/pterjan/rpmbuild/SOURCES/disable-update-check.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /home/pterjan/rpmbuild/SOURCES/CVE-2024-21501.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.evvjPo + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + cd glances-4.0.7 + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(packaging)' + echo 'python3dist(pip) >= 19' + '[' -f pyproject.toml ']' + true + for f in pyproject.toml setup.py setup.cfg + '[' -f pyproject.toml ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' pyproject.toml + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' pyproject.toml + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' pyproject.toml + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' pyproject.toml + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' pyproject.toml + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' pyproject.toml + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' pyproject.toml + sed -i -e 's/~=/>=/g' pyproject.toml + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' pyproject.toml + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' pyproject.toml + for f in pyproject.toml setup.py setup.cfg + '[' -f setup.py ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' setup.py + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' setup.py + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' setup.py + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' setup.py + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' setup.py + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' setup.py + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' setup.py + sed -i -e 's/~=/>=/g' setup.py + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' setup.py + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' setup.py + for f in pyproject.toml setup.py setup.cfg + '[' -f setup.cfg ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' setup.cfg + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' setup.cfg + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' setup.cfg + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' setup.cfg + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' setup.cfg + sed -i -e 's/~=/>=/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' setup.cfg + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' setup.cfg + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir + echo -n + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir + RPM_TOXENV=py313 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/pyproject-wheeldir --output /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 78.1.0) /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() 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' Handling tox-current-env >= 0.0.6 from tox itself Requirement satisfied: tox-current-env >= 0.0.6 (installed: tox-current-env 0.0.16) py313: OK (0.02 seconds) congratulations :) (0.08 seconds) Handling tox from tox --print-deps-only: py313 Requirement satisfied: tox (installed: tox 4.24.1) py313: OK (0.01 seconds) congratulations :) (0.07 seconds) running dist_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' creating '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/glances-4.0.7.dist-info' Handling defusedxml from hook generated metadata: Requires-Dist (Glances) Requirement satisfied: defusedxml (installed: defusedxml 0.8.0rc2) Handling packaging from hook generated metadata: Requires-Dist (Glances) Requirement satisfied: packaging (installed: packaging 24.2) Handling psutil>=5.6.7 from hook generated metadata: Requires-Dist (Glances) Requirement satisfied: psutil>=5.6.7 (installed: psutil 7.0.0) Handling ujson>=5.4.0 from hook generated metadata: Requires-Dist (Glances) Requirement satisfied: ujson>=5.4.0 (installed: ujson 5.10.0) Handling chevron; extra == "action" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: chevron; extra == "action" Handling zeroconf>=0.19.1; extra == "browser" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: zeroconf>=0.19.1; extra == "browser" Handling requests; extra == "cloud" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: requests; extra == "cloud" Handling docker>=6.1.1; extra == "containers" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: docker>=6.1.1; extra == "containers" Handling python-dateutil; extra == "containers" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: python-dateutil; extra == "containers" Handling six; extra == "containers" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: six; extra == "containers" Handling podman; extra == "containers" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: podman; extra == "containers" Handling packaging; extra == "containers" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: packaging; extra == "containers" Handling bernhard; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: bernhard; extra == "export" Handling cassandra-driver; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: cassandra-driver; extra == "export" Handling elasticsearch; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: elasticsearch; extra == "export" Handling graphitesender; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: graphitesender; extra == "export" Handling ibmcloudant; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: ibmcloudant; extra == "export" Handling influxdb>=1.0.0; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: influxdb>=1.0.0; extra == "export" Handling influxdb-client; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: influxdb-client; extra == "export" Handling pymongo; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pymongo; extra == "export" Handling kafka-python; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: kafka-python; extra == "export" Handling pika; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pika; extra == "export" Handling paho-mqtt; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: paho-mqtt; extra == "export" Handling potsdb; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: potsdb; extra == "export" Handling prometheus_client; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: prometheus_client; extra == "export" Handling pyzmq; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pyzmq; extra == "export" Handling statsd; extra == "export" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: statsd; extra == "export" Handling nvidia-ml-py; extra == "gpu" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: nvidia-ml-py; extra == "gpu" Handling pygal; extra == "graph" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pygal; extra == "graph" Handling netifaces; extra == "ip" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: netifaces; extra == "ip" Handling pymdstat; extra == "raid" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pymdstat; extra == "raid" Handling pySMART.smartx; extra == "smart" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pySMART.smartx; extra == "smart" Handling pysnmp; extra == "snmp" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pysnmp; extra == "snmp" Handling sparklines; extra == "sparklines" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: sparklines; extra == "sparklines" Handling fastapi; extra == "web" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: fastapi; extra == "web" Handling uvicorn; extra == "web" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: uvicorn; extra == "web" Handling jinja2; extra == "web" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: jinja2; extra == "web" Handling requests; extra == "web" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: requests; extra == "web" Handling wifi; extra == "wifi" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: wifi; extra == "wifi" Handling batinfo; extra == "sensors" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: batinfo; extra == "sensors" Handling chevron; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: chevron; extra == "all" Handling zeroconf>=0.19.1; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: zeroconf>=0.19.1; extra == "all" Handling requests; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: requests; extra == "all" Handling docker>=6.1.1; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: docker>=6.1.1; extra == "all" Handling bernhard; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: bernhard; extra == "all" Handling nvidia-ml-py; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: nvidia-ml-py; extra == "all" Handling pygal; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pygal; extra == "all" Handling netifaces; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: netifaces; extra == "all" Handling pymdstat; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pymdstat; extra == "all" Handling pySMART.smartx; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pySMART.smartx; extra == "all" Handling pysnmp; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: pysnmp; extra == "all" Handling sparklines; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: sparklines; extra == "all" Handling fastapi; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: fastapi; extra == "all" Handling wifi; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: wifi; extra == "all" Handling batinfo; extra == "all" from hook generated metadata: Requires-Dist (Glances) Ignoring alien requirement: batinfo; extra == "all" + cat /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-buildrequires + rm -rfv glances-4.0.7.dist-info/ removed 'glances-4.0.7.dist-info/entry_points.txt' removed 'glances-4.0.7.dist-info/top_level.txt' removed 'glances-4.0.7.dist-info/METADATA' removed 'glances-4.0.7.dist-info/licenses/AUTHORS' removed 'glances-4.0.7.dist-info/licenses/COPYING' removed directory 'glances-4.0.7.dist-info/licenses' removed directory 'glances-4.0.7.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.VP0VwL + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd glances-4.0.7 + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/pyproject-wheeldir Processing /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running dist_info creating /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info writing /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/PKG-INFO writing dependency_links to /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/dependency_links.txt writing entry points to /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/entry_points.txt writing requirements to /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/requires.txt writing top-level names to /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/top_level.txt writing manifest file '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/SOURCES.txt' reading manifest file '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'AUTHORS' writing manifest file '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/Glances.egg-info/SOURCES.txt' creating '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-modern-metadata-0lw1psb5/glances-4.0.7.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: Glances Building wheel for Glances (pyproject.toml): started Running command Building wheel for Glances (pyproject.toml) /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3) See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build/lib/glances copying glances/ports_list.py -> build/lib/glances copying glances/main.py -> build/lib/glances copying glances/folder_list.py -> build/lib/glances copying glances/actions.py -> build/lib/glances copying glances/static_list.py -> build/lib/glances copying glances/standalone.py -> build/lib/glances copying glances/thresholds.py -> build/lib/glances copying glances/timer.py -> build/lib/glances copying glances/webserver.py -> build/lib/glances copying glances/stats.py -> build/lib/glances copying glances/client.py -> build/lib/glances copying glances/amps_list.py -> build/lib/glances copying glances/stats_server.py -> build/lib/glances copying glances/server.py -> build/lib/glances copying glances/history.py -> build/lib/glances copying glances/logger.py -> build/lib/glances copying glances/cpu_percent.py -> build/lib/glances copying glances/__main__.py -> build/lib/glances copying glances/config.py -> build/lib/glances copying glances/password.py -> build/lib/glances copying glances/programs.py -> build/lib/glances copying glances/processes.py -> build/lib/glances copying glances/event.py -> build/lib/glances copying glances/client_browser.py -> build/lib/glances copying glances/events_list.py -> build/lib/glances copying glances/__init__.py -> build/lib/glances copying glances/globals.py -> build/lib/glances copying glances/secure.py -> build/lib/glances copying glances/outdated.py -> build/lib/glances copying glances/stats_client_snmp.py -> build/lib/glances copying glances/snmp.py -> build/lib/glances copying glances/attribute.py -> build/lib/glances copying glances/web_list.py -> build/lib/glances copying glances/stats_client.py -> build/lib/glances copying glances/filter.py -> build/lib/glances copying glances/password_list.py -> build/lib/glances copying glances/autodiscover.py -> build/lib/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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'glances.outputs.static.public' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.outputs.static.public' as an importable package[^1], but it is 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.public' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read 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.public' to be distributed and are already explicitly excluding 'glances.outputs.static.public' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'glances.plugins.__pycache__' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'glances.plugins.__pycache__' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'glances.plugins.__pycache__' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'glances.plugins.__pycache__' to be distributed and are already explicitly excluding 'glances.plugins.__pycache__' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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.13/site-packages/setuptools/command/build_py.py:212: _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/lib/glances/amps copying glances/amps/__init__.py -> build/lib/glances/amps copying glances/amps/amp.py -> build/lib/glances/amps creating build/lib/glances/amps/default copying glances/amps/default/__init__.py -> build/lib/glances/amps/default creating build/lib/glances/amps/nginx copying glances/amps/nginx/__init__.py -> build/lib/glances/amps/nginx creating build/lib/glances/amps/systemd copying glances/amps/systemd/__init__.py -> build/lib/glances/amps/systemd creating build/lib/glances/amps/systemv copying glances/amps/systemv/__init__.py -> build/lib/glances/amps/systemv creating build/lib/glances/exports copying glances/exports/__init__.py -> build/lib/glances/exports copying glances/exports/export.py -> build/lib/glances/exports creating build/lib/glances/exports/glances_cassandra copying glances/exports/glances_cassandra/__init__.py -> build/lib/glances/exports/glances_cassandra creating build/lib/glances/exports/glances_couchdb copying glances/exports/glances_couchdb/__init__.py -> build/lib/glances/exports/glances_couchdb creating build/lib/glances/exports/glances_csv copying glances/exports/glances_csv/__init__.py -> build/lib/glances/exports/glances_csv creating build/lib/glances/exports/glances_elasticsearch copying glances/exports/glances_elasticsearch/__init__.py -> build/lib/glances/exports/glances_elasticsearch creating build/lib/glances/exports/glances_graph copying glances/exports/glances_graph/__init__.py -> build/lib/glances/exports/glances_graph creating build/lib/glances/exports/glances_graphite copying glances/exports/glances_graphite/__init__.py -> build/lib/glances/exports/glances_graphite creating build/lib/glances/exports/glances_influxdb copying glances/exports/glances_influxdb/__init__.py -> build/lib/glances/exports/glances_influxdb creating build/lib/glances/exports/glances_influxdb2 copying glances/exports/glances_influxdb2/__init__.py -> build/lib/glances/exports/glances_influxdb2 creating build/lib/glances/exports/glances_json copying glances/exports/glances_json/__init__.py -> build/lib/glances/exports/glances_json creating build/lib/glances/exports/glances_kafka copying glances/exports/glances_kafka/__init__.py -> build/lib/glances/exports/glances_kafka creating build/lib/glances/exports/glances_mongodb copying glances/exports/glances_mongodb/__init__.py -> build/lib/glances/exports/glances_mongodb creating build/lib/glances/exports/glances_mqtt copying glances/exports/glances_mqtt/__init__.py -> build/lib/glances/exports/glances_mqtt creating build/lib/glances/exports/glances_opentsdb copying glances/exports/glances_opentsdb/__init__.py -> build/lib/glances/exports/glances_opentsdb creating build/lib/glances/exports/glances_prometheus copying glances/exports/glances_prometheus/__init__.py -> build/lib/glances/exports/glances_prometheus creating build/lib/glances/exports/glances_rabbitmq copying glances/exports/glances_rabbitmq/__init__.py -> build/lib/glances/exports/glances_rabbitmq creating build/lib/glances/exports/glances_restful copying glances/exports/glances_restful/__init__.py -> build/lib/glances/exports/glances_restful creating build/lib/glances/exports/glances_riemann copying glances/exports/glances_riemann/__init__.py -> build/lib/glances/exports/glances_riemann creating build/lib/glances/exports/glances_statsd copying glances/exports/glances_statsd/__init__.py -> build/lib/glances/exports/glances_statsd creating build/lib/glances/exports/glances_zeromq copying glances/exports/glances_zeromq/__init__.py -> build/lib/glances/exports/glances_zeromq creating build/lib/glances/outputs copying glances/outputs/__init__.py -> build/lib/glances/outputs copying glances/outputs/glances_bars.py -> build/lib/glances/outputs copying glances/outputs/glances_curses.py -> build/lib/glances/outputs copying glances/outputs/glances_curses_browser.py -> build/lib/glances/outputs copying glances/outputs/glances_restful_api.py -> build/lib/glances/outputs copying glances/outputs/glances_sparklines.py -> build/lib/glances/outputs copying glances/outputs/glances_stdout.py -> build/lib/glances/outputs copying glances/outputs/glances_stdout_apidoc.py -> build/lib/glances/outputs copying glances/outputs/glances_stdout_csv.py -> build/lib/glances/outputs copying glances/outputs/glances_stdout_issue.py -> build/lib/glances/outputs copying glances/outputs/glances_stdout_json.py -> build/lib/glances/outputs copying glances/outputs/glances_unicode.py -> build/lib/glances/outputs creating build/lib/glances/outputs/static copying glances/outputs/static/.eslintrc.js -> build/lib/glances/outputs/static copying glances/outputs/static/.prettierrc.js -> build/lib/glances/outputs/static copying glances/outputs/static/README.md -> build/lib/glances/outputs/static copying glances/outputs/static/package-lock.json -> build/lib/glances/outputs/static copying glances/outputs/static/package.json -> build/lib/glances/outputs/static copying glances/outputs/static/webpack.config.js -> build/lib/glances/outputs/static creating build/lib/glances/outputs/static/css copying glances/outputs/static/css/bootstrap.less -> build/lib/glances/outputs/static/css copying glances/outputs/static/css/style.scss -> build/lib/glances/outputs/static/css copying glances/outputs/static/css/variables.less -> build/lib/glances/outputs/static/css creating build/lib/glances/outputs/static/images copying glances/outputs/static/images/favicon.ico -> build/lib/glances/outputs/static/images copying glances/outputs/static/images/glances.png -> build/lib/glances/outputs/static/images creating build/lib/glances/outputs/static/js copying glances/outputs/static/js/App.vue -> build/lib/glances/outputs/static/js copying glances/outputs/static/js/app.js -> build/lib/glances/outputs/static/js copying glances/outputs/static/js/filters.js -> build/lib/glances/outputs/static/js copying glances/outputs/static/js/services.js -> build/lib/glances/outputs/static/js copying glances/outputs/static/js/store.js -> build/lib/glances/outputs/static/js copying glances/outputs/static/js/uiconfig.json -> build/lib/glances/outputs/static/js creating build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/help.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-alert.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-amps.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-cloud.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-connections.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-containers.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-cpu.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-diskio.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-folders.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-fs.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-gpu.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-ip.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-irq.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-load.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-mem-more.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-mem.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-memswap.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-network.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-now.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-percpu.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-ports.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-process.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-processcount.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-processlist.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-quicklook.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-raid.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-sensors.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-smart.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-system.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-uptime.vue -> build/lib/glances/outputs/static/js/components copying glances/outputs/static/js/components/plugin-wifi.vue -> build/lib/glances/outputs/static/js/components creating build/lib/glances/outputs/static/public copying glances/outputs/static/public/1272f6e9e8f9d6bfd6de.png -> build/lib/glances/outputs/static/public copying glances/outputs/static/public/favicon.ico -> build/lib/glances/outputs/static/public copying glances/outputs/static/public/glances.js -> build/lib/glances/outputs/static/public creating build/lib/glances/outputs/static/templates copying glances/outputs/static/templates/index.html -> build/lib/glances/outputs/static/templates creating build/lib/glances/plugins copying glances/plugins/__init__.py -> build/lib/glances/plugins creating build/lib/glances/plugins/__pycache__ copying glances/plugins/__pycache__/__init__.py -> build/lib/glances/plugins/__pycache__ creating build/lib/glances/plugins/alert copying glances/plugins/alert/__init__.py -> build/lib/glances/plugins/alert creating build/lib/glances/plugins/amps copying glances/plugins/amps/__init__.py -> build/lib/glances/plugins/amps creating build/lib/glances/plugins/cloud copying glances/plugins/cloud/__init__.py -> build/lib/glances/plugins/cloud creating build/lib/glances/plugins/connections copying glances/plugins/connections/__init__.py -> build/lib/glances/plugins/connections creating build/lib/glances/plugins/containers copying glances/plugins/containers/__init__.py -> build/lib/glances/plugins/containers copying glances/plugins/containers/stats_streamer.py -> build/lib/glances/plugins/containers creating build/lib/glances/plugins/containers/engines copying glances/plugins/containers/engines/__init__.py -> build/lib/glances/plugins/containers/engines copying glances/plugins/containers/engines/docker.py -> build/lib/glances/plugins/containers/engines copying glances/plugins/containers/engines/podman.py -> build/lib/glances/plugins/containers/engines creating build/lib/glances/plugins/core copying glances/plugins/core/__init__.py -> build/lib/glances/plugins/core creating build/lib/glances/plugins/cpu copying glances/plugins/cpu/__init__.py -> build/lib/glances/plugins/cpu creating build/lib/glances/plugins/diskio copying glances/plugins/diskio/__init__.py -> build/lib/glances/plugins/diskio creating build/lib/glances/plugins/folders copying glances/plugins/folders/__init__.py -> build/lib/glances/plugins/folders creating build/lib/glances/plugins/fs copying glances/plugins/fs/__init__.py -> build/lib/glances/plugins/fs creating build/lib/glances/plugins/gpu copying glances/plugins/gpu/__init__.py -> build/lib/glances/plugins/gpu creating build/lib/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/__init__.py -> build/lib/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/amd.py -> build/lib/glances/plugins/gpu/cards copying glances/plugins/gpu/cards/nvidia.py -> build/lib/glances/plugins/gpu/cards creating build/lib/glances/plugins/help copying glances/plugins/help/__init__.py -> build/lib/glances/plugins/help creating build/lib/glances/plugins/ip copying glances/plugins/ip/__init__.py -> build/lib/glances/plugins/ip creating build/lib/glances/plugins/irq copying glances/plugins/irq/__init__.py -> build/lib/glances/plugins/irq creating build/lib/glances/plugins/load copying glances/plugins/load/__init__.py -> build/lib/glances/plugins/load creating build/lib/glances/plugins/mem copying glances/plugins/mem/__init__.py -> build/lib/glances/plugins/mem creating build/lib/glances/plugins/memswap copying glances/plugins/memswap/__init__.py -> build/lib/glances/plugins/memswap creating build/lib/glances/plugins/network copying glances/plugins/network/__init__.py -> build/lib/glances/plugins/network creating build/lib/glances/plugins/now copying glances/plugins/now/__init__.py -> build/lib/glances/plugins/now creating build/lib/glances/plugins/percpu copying glances/plugins/percpu/__init__.py -> build/lib/glances/plugins/percpu creating build/lib/glances/plugins/plugin copying glances/plugins/plugin/__init__.py -> build/lib/glances/plugins/plugin copying glances/plugins/plugin/model.py -> build/lib/glances/plugins/plugin creating build/lib/glances/plugins/ports copying glances/plugins/ports/__init__.py -> build/lib/glances/plugins/ports creating build/lib/glances/plugins/processcount copying glances/plugins/processcount/__init__.py -> build/lib/glances/plugins/processcount creating build/lib/glances/plugins/processlist copying glances/plugins/processlist/__init__.py -> build/lib/glances/plugins/processlist creating build/lib/glances/plugins/psutilversion copying glances/plugins/psutilversion/__init__.py -> build/lib/glances/plugins/psutilversion creating build/lib/glances/plugins/quicklook copying glances/plugins/quicklook/__init__.py -> build/lib/glances/plugins/quicklook creating build/lib/glances/plugins/raid copying glances/plugins/raid/__init__.py -> build/lib/glances/plugins/raid creating build/lib/glances/plugins/sensors copying glances/plugins/sensors/__init__.py -> build/lib/glances/plugins/sensors creating build/lib/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/__init__.py -> build/lib/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/glances_batpercent.py -> build/lib/glances/plugins/sensors/sensor copying glances/plugins/sensors/sensor/glances_hddtemp.py -> build/lib/glances/plugins/sensors/sensor creating build/lib/glances/plugins/smart copying glances/plugins/smart/__init__.py -> build/lib/glances/plugins/smart creating build/lib/glances/plugins/system copying glances/plugins/system/__init__.py -> build/lib/glances/plugins/system creating build/lib/glances/plugins/uptime copying glances/plugins/uptime/__init__.py -> build/lib/glances/plugins/uptime creating build/lib/glances/plugins/version copying glances/plugins/version/__init__.py -> build/lib/glances/plugins/version creating build/lib/glances/plugins/wifi copying glances/plugins/wifi/__init__.py -> build/lib/glances/plugins/wifi installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/glances copying build/lib/glances/ports_list.py -> build/bdist.linux-x86_64/wheel/./glances creating build/bdist.linux-x86_64/wheel/glances/plugins creating build/bdist.linux-x86_64/wheel/glances/plugins/now copying build/lib/glances/plugins/now/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/now creating build/bdist.linux-x86_64/wheel/glances/plugins/__pycache__ copying build/lib/glances/plugins/__pycache__/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/__pycache__ creating build/bdist.linux-x86_64/wheel/glances/plugins/containers copying build/lib/glances/plugins/containers/stats_streamer.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/containers creating build/bdist.linux-x86_64/wheel/glances/plugins/containers/engines copying build/lib/glances/plugins/containers/engines/docker.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/containers/engines copying build/lib/glances/plugins/containers/engines/podman.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/containers/engines copying build/lib/glances/plugins/containers/engines/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/containers/engines copying build/lib/glances/plugins/containers/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/containers creating build/bdist.linux-x86_64/wheel/glances/plugins/ip copying build/lib/glances/plugins/ip/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/ip creating build/bdist.linux-x86_64/wheel/glances/plugins/uptime copying build/lib/glances/plugins/uptime/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/uptime creating build/bdist.linux-x86_64/wheel/glances/plugins/processcount copying build/lib/glances/plugins/processcount/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/processcount creating build/bdist.linux-x86_64/wheel/glances/plugins/psutilversion copying build/lib/glances/plugins/psutilversion/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/psutilversion creating build/bdist.linux-x86_64/wheel/glances/plugins/load copying build/lib/glances/plugins/load/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/load creating build/bdist.linux-x86_64/wheel/glances/plugins/raid copying build/lib/glances/plugins/raid/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/raid creating build/bdist.linux-x86_64/wheel/glances/plugins/core copying build/lib/glances/plugins/core/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/core creating build/bdist.linux-x86_64/wheel/glances/plugins/plugin copying build/lib/glances/plugins/plugin/model.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/plugin copying build/lib/glances/plugins/plugin/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/plugin creating build/bdist.linux-x86_64/wheel/glances/plugins/diskio copying build/lib/glances/plugins/diskio/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/diskio creating build/bdist.linux-x86_64/wheel/glances/plugins/irq copying build/lib/glances/plugins/irq/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/irq creating build/bdist.linux-x86_64/wheel/glances/plugins/memswap copying build/lib/glances/plugins/memswap/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/memswap creating build/bdist.linux-x86_64/wheel/glances/plugins/connections copying build/lib/glances/plugins/connections/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/connections creating build/bdist.linux-x86_64/wheel/glances/plugins/fs copying build/lib/glances/plugins/fs/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/fs creating build/bdist.linux-x86_64/wheel/glances/plugins/amps copying build/lib/glances/plugins/amps/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/amps creating build/bdist.linux-x86_64/wheel/glances/plugins/cpu copying build/lib/glances/plugins/cpu/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/cpu creating build/bdist.linux-x86_64/wheel/glances/plugins/cloud copying build/lib/glances/plugins/cloud/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/cloud copying build/lib/glances/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins creating build/bdist.linux-x86_64/wheel/glances/plugins/smart copying build/lib/glances/plugins/smart/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/smart creating build/bdist.linux-x86_64/wheel/glances/plugins/gpu creating build/bdist.linux-x86_64/wheel/glances/plugins/gpu/cards copying build/lib/glances/plugins/gpu/cards/amd.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/gpu/cards copying build/lib/glances/plugins/gpu/cards/nvidia.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/gpu/cards copying build/lib/glances/plugins/gpu/cards/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/gpu/cards copying build/lib/glances/plugins/gpu/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/gpu creating build/bdist.linux-x86_64/wheel/glances/plugins/wifi copying build/lib/glances/plugins/wifi/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/wifi creating build/bdist.linux-x86_64/wheel/glances/plugins/help copying build/lib/glances/plugins/help/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/help creating build/bdist.linux-x86_64/wheel/glances/plugins/quicklook copying build/lib/glances/plugins/quicklook/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/quicklook creating build/bdist.linux-x86_64/wheel/glances/plugins/processlist copying build/lib/glances/plugins/processlist/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/processlist creating build/bdist.linux-x86_64/wheel/glances/plugins/mem copying build/lib/glances/plugins/mem/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/mem creating build/bdist.linux-x86_64/wheel/glances/plugins/ports copying build/lib/glances/plugins/ports/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/ports creating build/bdist.linux-x86_64/wheel/glances/plugins/sensors creating build/bdist.linux-x86_64/wheel/glances/plugins/sensors/sensor copying build/lib/glances/plugins/sensors/sensor/glances_hddtemp.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/sensors/sensor copying build/lib/glances/plugins/sensors/sensor/glances_batpercent.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/sensors/sensor copying build/lib/glances/plugins/sensors/sensor/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/sensors/sensor copying build/lib/glances/plugins/sensors/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/sensors creating build/bdist.linux-x86_64/wheel/glances/plugins/alert copying build/lib/glances/plugins/alert/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/alert creating build/bdist.linux-x86_64/wheel/glances/plugins/version copying build/lib/glances/plugins/version/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/version creating build/bdist.linux-x86_64/wheel/glances/plugins/percpu copying build/lib/glances/plugins/percpu/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/percpu creating build/bdist.linux-x86_64/wheel/glances/plugins/system copying build/lib/glances/plugins/system/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/system creating build/bdist.linux-x86_64/wheel/glances/plugins/network copying build/lib/glances/plugins/network/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/network creating build/bdist.linux-x86_64/wheel/glances/plugins/folders copying build/lib/glances/plugins/folders/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/plugins/folders copying build/lib/glances/main.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/folder_list.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/actions.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/static_list.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/standalone.py -> build/bdist.linux-x86_64/wheel/./glances creating build/bdist.linux-x86_64/wheel/glances/outputs copying build/lib/glances/outputs/glances_restful_api.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_sparklines.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_stdout_issue.py -> build/bdist.linux-x86_64/wheel/./glances/outputs creating build/bdist.linux-x86_64/wheel/glances/outputs/static creating build/bdist.linux-x86_64/wheel/glances/outputs/static/css copying build/lib/glances/outputs/static/css/bootstrap.less -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/css copying build/lib/glances/outputs/static/css/style.scss -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/css copying build/lib/glances/outputs/static/css/variables.less -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/css copying build/lib/glances/outputs/static/package.json -> build/bdist.linux-x86_64/wheel/./glances/outputs/static copying build/lib/glances/outputs/static/webpack.config.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static copying build/lib/glances/outputs/static/package-lock.json -> build/bdist.linux-x86_64/wheel/./glances/outputs/static creating build/bdist.linux-x86_64/wheel/glances/outputs/static/templates copying build/lib/glances/outputs/static/templates/index.html -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/templates creating build/bdist.linux-x86_64/wheel/glances/outputs/static/public copying build/lib/glances/outputs/static/public/1272f6e9e8f9d6bfd6de.png -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/public copying build/lib/glances/outputs/static/public/glances.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/public copying build/lib/glances/outputs/static/public/favicon.ico -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/public creating build/bdist.linux-x86_64/wheel/glances/outputs/static/images copying build/lib/glances/outputs/static/images/glances.png -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/images copying build/lib/glances/outputs/static/images/favicon.ico -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/images creating build/bdist.linux-x86_64/wheel/glances/outputs/static/js copying build/lib/glances/outputs/static/js/services.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js copying build/lib/glances/outputs/static/js/App.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js creating build/bdist.linux-x86_64/wheel/glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-fs.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-ports.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-percpu.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-cpu.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/help.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-diskio.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-cloud.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-network.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-process.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-load.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-system.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-uptime.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-now.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-alert.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-processlist.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-sensors.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-irq.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-smart.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-amps.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-processcount.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-ip.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-mem-more.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-gpu.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-memswap.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-containers.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-raid.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-mem.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-quicklook.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-connections.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-folders.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/components/plugin-wifi.vue -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js/components copying build/lib/glances/outputs/static/js/app.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js copying build/lib/glances/outputs/static/js/store.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js copying build/lib/glances/outputs/static/js/uiconfig.json -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js copying build/lib/glances/outputs/static/js/filters.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static/js copying build/lib/glances/outputs/static/.eslintrc.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static copying build/lib/glances/outputs/static/.prettierrc.js -> build/bdist.linux-x86_64/wheel/./glances/outputs/static copying build/lib/glances/outputs/static/README.md -> build/bdist.linux-x86_64/wheel/./glances/outputs/static copying build/lib/glances/outputs/glances_stdout_csv.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_stdout_json.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_curses_browser.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_curses.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_stdout_apidoc.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_bars.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_unicode.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/outputs/glances_stdout.py -> build/bdist.linux-x86_64/wheel/./glances/outputs copying build/lib/glances/thresholds.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/timer.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/webserver.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/stats.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/client.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/amps_list.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/stats_server.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/server.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/history.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/logger.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/cpu_percent.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/__main__.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/config.py -> build/bdist.linux-x86_64/wheel/./glances creating build/bdist.linux-x86_64/wheel/glances/amps creating build/bdist.linux-x86_64/wheel/glances/amps/nginx copying build/lib/glances/amps/nginx/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/amps/nginx creating build/bdist.linux-x86_64/wheel/glances/amps/systemd copying build/lib/glances/amps/systemd/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/amps/systemd creating build/bdist.linux-x86_64/wheel/glances/amps/default copying build/lib/glances/amps/default/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/amps/default creating build/bdist.linux-x86_64/wheel/glances/amps/systemv copying build/lib/glances/amps/systemv/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/amps/systemv copying build/lib/glances/amps/amp.py -> build/bdist.linux-x86_64/wheel/./glances/amps copying build/lib/glances/amps/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/amps copying build/lib/glances/password.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/programs.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/processes.py -> build/bdist.linux-x86_64/wheel/./glances creating build/bdist.linux-x86_64/wheel/glances/exports creating build/bdist.linux-x86_64/wheel/glances/exports/glances_couchdb copying build/lib/glances/exports/glances_couchdb/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_couchdb copying build/lib/glances/exports/export.py -> build/bdist.linux-x86_64/wheel/./glances/exports creating build/bdist.linux-x86_64/wheel/glances/exports/glances_influxdb copying build/lib/glances/exports/glances_influxdb/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_influxdb creating build/bdist.linux-x86_64/wheel/glances/exports/glances_rabbitmq copying build/lib/glances/exports/glances_rabbitmq/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_rabbitmq creating build/bdist.linux-x86_64/wheel/glances/exports/glances_mongodb copying build/lib/glances/exports/glances_mongodb/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_mongodb creating build/bdist.linux-x86_64/wheel/glances/exports/glances_elasticsearch copying build/lib/glances/exports/glances_elasticsearch/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_elasticsearch creating build/bdist.linux-x86_64/wheel/glances/exports/glances_graph copying build/lib/glances/exports/glances_graph/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_graph creating build/bdist.linux-x86_64/wheel/glances/exports/glances_graphite copying build/lib/glances/exports/glances_graphite/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_graphite creating build/bdist.linux-x86_64/wheel/glances/exports/glances_prometheus copying build/lib/glances/exports/glances_prometheus/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_prometheus creating build/bdist.linux-x86_64/wheel/glances/exports/glances_kafka copying build/lib/glances/exports/glances_kafka/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_kafka creating build/bdist.linux-x86_64/wheel/glances/exports/glances_mqtt copying build/lib/glances/exports/glances_mqtt/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_mqtt creating build/bdist.linux-x86_64/wheel/glances/exports/glances_zeromq copying build/lib/glances/exports/glances_zeromq/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_zeromq creating build/bdist.linux-x86_64/wheel/glances/exports/glances_restful copying build/lib/glances/exports/glances_restful/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_restful creating build/bdist.linux-x86_64/wheel/glances/exports/glances_cassandra copying build/lib/glances/exports/glances_cassandra/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_cassandra creating build/bdist.linux-x86_64/wheel/glances/exports/glances_csv copying build/lib/glances/exports/glances_csv/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_csv creating build/bdist.linux-x86_64/wheel/glances/exports/glances_json copying build/lib/glances/exports/glances_json/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_json creating build/bdist.linux-x86_64/wheel/glances/exports/glances_riemann copying build/lib/glances/exports/glances_riemann/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_riemann creating build/bdist.linux-x86_64/wheel/glances/exports/glances_influxdb2 copying build/lib/glances/exports/glances_influxdb2/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_influxdb2 copying build/lib/glances/exports/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports creating build/bdist.linux-x86_64/wheel/glances/exports/glances_opentsdb copying build/lib/glances/exports/glances_opentsdb/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_opentsdb creating build/bdist.linux-x86_64/wheel/glances/exports/glances_statsd copying build/lib/glances/exports/glances_statsd/__init__.py -> build/bdist.linux-x86_64/wheel/./glances/exports/glances_statsd copying build/lib/glances/event.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/client_browser.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/events_list.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/__init__.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/globals.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/secure.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/outdated.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/stats_client_snmp.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/snmp.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/attribute.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/web_list.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/stats_client.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/filter.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/password_list.py -> build/bdist.linux-x86_64/wheel/./glances copying build/lib/glances/autodiscover.py -> build/bdist.linux-x86_64/wheel/./glances running install_data creating build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data creating build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying AUTHORS -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying COPYING -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying NEWS.rst -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying README.rst -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying SECURITY.md -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances copying conf/glances.conf -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/doc/glances creating build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/man/man1 copying docs/man/glances.1 -> build/bdist.linux-x86_64/wheel/glances-4.0.7.data/data/share/man/man1 running install_egg_info Copying Glances.egg-info to build/bdist.linux-x86_64/wheel/./Glances-4.0.7-py3.13.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/glances-4.0.7.dist-info/WHEEL creating '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir/pip-wheel-0n8bdld1/.tmp-6w2ozaj9/glances-4.0.7-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'glances/__init__.py' adding 'glances/__main__.py' adding 'glances/actions.py' adding 'glances/amps_list.py' adding 'glances/attribute.py' adding 'glances/autodiscover.py' adding 'glances/client.py' adding 'glances/client_browser.py' adding 'glances/config.py' adding 'glances/cpu_percent.py' adding 'glances/event.py' adding 'glances/events_list.py' adding 'glances/filter.py' adding 'glances/folder_list.py' adding 'glances/globals.py' adding 'glances/history.py' adding 'glances/logger.py' adding 'glances/main.py' adding 'glances/outdated.py' adding 'glances/password.py' adding 'glances/password_list.py' adding 'glances/ports_list.py' adding 'glances/processes.py' adding 'glances/programs.py' adding 'glances/secure.py' adding 'glances/server.py' adding 'glances/snmp.py' adding 'glances/standalone.py' adding 'glances/static_list.py' adding 'glances/stats.py' adding 'glances/stats_client.py' adding 'glances/stats_client_snmp.py' adding 'glances/stats_server.py' adding 'glances/thresholds.py' adding 'glances/timer.py' adding 'glances/web_list.py' adding 'glances/webserver.py' adding 'glances/amps/__init__.py' adding 'glances/amps/amp.py' adding 'glances/amps/default/__init__.py' adding 'glances/amps/nginx/__init__.py' adding 'glances/amps/systemd/__init__.py' adding 'glances/amps/systemv/__init__.py' adding 'glances/exports/__init__.py' adding 'glances/exports/export.py' adding 'glances/exports/glances_cassandra/__init__.py' adding 'glances/exports/glances_couchdb/__init__.py' adding 'glances/exports/glances_csv/__init__.py' adding 'glances/exports/glances_elasticsearch/__init__.py' adding 'glances/exports/glances_graph/__init__.py' adding 'glances/exports/glances_graphite/__init__.py' adding 'glances/exports/glances_influxdb/__init__.py' adding 'glances/exports/glances_influxdb2/__init__.py' adding 'glances/exports/glances_json/__init__.py' adding 'glances/exports/glances_kafka/__init__.py' adding 'glances/exports/glances_mongodb/__init__.py' adding 'glances/exports/glances_mqtt/__init__.py' adding 'glances/exports/glances_opentsdb/__init__.py' adding 'glances/exports/glances_prometheus/__init__.py' adding 'glances/exports/glances_rabbitmq/__init__.py' adding 'glances/exports/glances_restful/__init__.py' adding 'glances/exports/glances_riemann/__init__.py' adding 'glances/exports/glances_statsd/__init__.py' adding 'glances/exports/glances_zeromq/__init__.py' adding 'glances/outputs/__init__.py' adding 'glances/outputs/glances_bars.py' adding 'glances/outputs/glances_curses.py' adding 'glances/outputs/glances_curses_browser.py' adding 'glances/outputs/glances_restful_api.py' adding 'glances/outputs/glances_sparklines.py' adding 'glances/outputs/glances_stdout.py' adding 'glances/outputs/glances_stdout_apidoc.py' adding 'glances/outputs/glances_stdout_csv.py' adding 'glances/outputs/glances_stdout_issue.py' adding 'glances/outputs/glances_stdout_json.py' adding 'glances/outputs/glances_unicode.py' adding 'glances/outputs/static/.eslintrc.js' adding 'glances/outputs/static/.prettierrc.js' adding 'glances/outputs/static/README.md' adding 'glances/outputs/static/package-lock.json' adding 'glances/outputs/static/package.json' adding 'glances/outputs/static/webpack.config.js' adding 'glances/outputs/static/css/bootstrap.less' adding 'glances/outputs/static/css/style.scss' adding 'glances/outputs/static/css/variables.less' adding 'glances/outputs/static/images/favicon.ico' adding 'glances/outputs/static/images/glances.png' adding 'glances/outputs/static/js/App.vue' adding 'glances/outputs/static/js/app.js' adding 'glances/outputs/static/js/filters.js' adding 'glances/outputs/static/js/services.js' adding 'glances/outputs/static/js/store.js' adding 'glances/outputs/static/js/uiconfig.json' adding 'glances/outputs/static/js/components/help.vue' adding 'glances/outputs/static/js/components/plugin-alert.vue' adding 'glances/outputs/static/js/components/plugin-amps.vue' adding 'glances/outputs/static/js/components/plugin-cloud.vue' adding 'glances/outputs/static/js/components/plugin-connections.vue' adding 'glances/outputs/static/js/components/plugin-containers.vue' adding 'glances/outputs/static/js/components/plugin-cpu.vue' adding 'glances/outputs/static/js/components/plugin-diskio.vue' adding 'glances/outputs/static/js/components/plugin-folders.vue' adding 'glances/outputs/static/js/components/plugin-fs.vue' adding 'glances/outputs/static/js/components/plugin-gpu.vue' adding 'glances/outputs/static/js/components/plugin-ip.vue' adding 'glances/outputs/static/js/components/plugin-irq.vue' adding 'glances/outputs/static/js/components/plugin-load.vue' adding 'glances/outputs/static/js/components/plugin-mem-more.vue' adding 'glances/outputs/static/js/components/plugin-mem.vue' adding 'glances/outputs/static/js/components/plugin-memswap.vue' adding 'glances/outputs/static/js/components/plugin-network.vue' adding 'glances/outputs/static/js/components/plugin-now.vue' adding 'glances/outputs/static/js/components/plugin-percpu.vue' adding 'glances/outputs/static/js/components/plugin-ports.vue' adding 'glances/outputs/static/js/components/plugin-process.vue' adding 'glances/outputs/static/js/components/plugin-processcount.vue' adding 'glances/outputs/static/js/components/plugin-processlist.vue' adding 'glances/outputs/static/js/components/plugin-quicklook.vue' adding 'glances/outputs/static/js/components/plugin-raid.vue' adding 'glances/outputs/static/js/components/plugin-sensors.vue' adding 'glances/outputs/static/js/components/plugin-smart.vue' adding 'glances/outputs/static/js/components/plugin-system.vue' adding 'glances/outputs/static/js/components/plugin-uptime.vue' adding 'glances/outputs/static/js/components/plugin-wifi.vue' adding 'glances/outputs/static/public/1272f6e9e8f9d6bfd6de.png' adding 'glances/outputs/static/public/favicon.ico' adding 'glances/outputs/static/public/glances.js' adding 'glances/outputs/static/templates/index.html' adding 'glances/plugins/__init__.py' adding 'glances/plugins/__pycache__/__init__.py' adding 'glances/plugins/alert/__init__.py' adding 'glances/plugins/amps/__init__.py' adding 'glances/plugins/cloud/__init__.py' adding 'glances/plugins/connections/__init__.py' adding 'glances/plugins/containers/__init__.py' adding 'glances/plugins/containers/stats_streamer.py' adding 'glances/plugins/containers/engines/__init__.py' adding 'glances/plugins/containers/engines/docker.py' adding 'glances/plugins/containers/engines/podman.py' adding 'glances/plugins/core/__init__.py' adding 'glances/plugins/cpu/__init__.py' adding 'glances/plugins/diskio/__init__.py' adding 'glances/plugins/folders/__init__.py' adding 'glances/plugins/fs/__init__.py' adding 'glances/plugins/gpu/__init__.py' adding 'glances/plugins/gpu/cards/__init__.py' adding 'glances/plugins/gpu/cards/amd.py' adding 'glances/plugins/gpu/cards/nvidia.py' adding 'glances/plugins/help/__init__.py' adding 'glances/plugins/ip/__init__.py' adding 'glances/plugins/irq/__init__.py' adding 'glances/plugins/load/__init__.py' adding 'glances/plugins/mem/__init__.py' adding 'glances/plugins/memswap/__init__.py' adding 'glances/plugins/network/__init__.py' adding 'glances/plugins/now/__init__.py' adding 'glances/plugins/percpu/__init__.py' adding 'glances/plugins/plugin/__init__.py' adding 'glances/plugins/plugin/model.py' adding 'glances/plugins/ports/__init__.py' adding 'glances/plugins/processcount/__init__.py' adding 'glances/plugins/processlist/__init__.py' adding 'glances/plugins/psutilversion/__init__.py' adding 'glances/plugins/quicklook/__init__.py' adding 'glances/plugins/raid/__init__.py' adding 'glances/plugins/sensors/__init__.py' adding 'glances/plugins/sensors/sensor/__init__.py' adding 'glances/plugins/sensors/sensor/glances_batpercent.py' adding 'glances/plugins/sensors/sensor/glances_hddtemp.py' adding 'glances/plugins/smart/__init__.py' adding 'glances/plugins/system/__init__.py' adding 'glances/plugins/uptime/__init__.py' adding 'glances/plugins/version/__init__.py' adding 'glances/plugins/wifi/__init__.py' adding 'glances-4.0.7.data/data/share/doc/glances/AUTHORS' adding 'glances-4.0.7.data/data/share/doc/glances/CONTRIBUTING.md' adding 'glances-4.0.7.data/data/share/doc/glances/COPYING' adding 'glances-4.0.7.data/data/share/doc/glances/NEWS.rst' adding 'glances-4.0.7.data/data/share/doc/glances/README.rst' adding 'glances-4.0.7.data/data/share/doc/glances/SECURITY.md' adding 'glances-4.0.7.data/data/share/doc/glances/glances.conf' adding 'glances-4.0.7.data/data/share/man/man1/glances.1' adding 'glances-4.0.7.dist-info/licenses/AUTHORS' adding 'glances-4.0.7.dist-info/licenses/COPYING' adding 'glances-4.0.7.dist-info/METADATA' adding 'glances-4.0.7.dist-info/WHEEL' adding 'glances-4.0.7.dist-info/entry_points.txt' adding 'glances-4.0.7.dist-info/top_level.txt' adding 'glances-4.0.7.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Building wheel for Glances (pyproject.toml): finished with status 'done' Created wheel for Glances: filename=glances-4.0.7-py3-none-any.whl size=736766 sha256=c56e5df285e51cb8af96411b46626981791052d4432c8d8100cb96b68872c492 Stored in directory: /home/pterjan/.cache/pip/wheels/5e/ba/df/5e303787596fa6d947a38cb3a639cc1f7bcad7ad35638a8f48 Successfully built Glances + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.scNWRv + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + '[' 1 -eq 1 ']' + '[' /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT '!=' / ']' + rm -rf /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT ++ dirname /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT + mkdir -p /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + mkdir /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd glances-4.0.7 + '[' 1 -eq 1 ']' ++ ls /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/pyproject-wheeldir/glances-4.0.7-py3-none-any.whl ++ xargs basename --multiple ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=glances==4.0.7 + '[' -z glances==4.0.7 ']' + TMPDIR=/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/.pyproject-builddir + /usr/bin/python3 -m pip install --root /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/pyproject-wheeldir glances==4.0.7 Using pip 25.0.1 from /usr/lib/python3.13/site-packages/pip (python 3.13) Looking in links: /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/pyproject-wheeldir Processing ./pyproject-wheeldir/glances-4.0.7-py3-none-any.whl Installing collected packages: glances Creating /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/bin changing mode of /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/bin/glances to 755 Successfully installed glances-4.0.7 + '[' -d /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/bin ']' + '[' -z sP ']' + shebang_flags=-kasP + /usr/bin/python3 -B /usr/lib/rpm/redhat/pathfix.py -pni /usr/bin/python3 -kasP /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/bin/glances /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/bin/glances: updating + rm -rfv /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/bin/__pycache__ + rm -f /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-ghost-distinfo + site_dirs=() + '[' -d /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + site_dirs+=("/usr/lib/python3.13/site-packages") + '[' /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib64/python3.13/site-packages '!=' /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + '[' -d /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib64/python3.13/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.13/site-packages/glances-4.0.7.dist-info' + sed -i s/pip/rpm/ /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages/glances-4.0.7.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/redhat + /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT --record /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages/glances-4.0.7.dist-info/RECORD --output /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-record + rm -fv /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages/glances-4.0.7.dist-info/RECORD removed '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages/glances-4.0.7.dist-info/RECORD' + rm -fv /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages/glances-4.0.7.dist-info/REQUESTED removed '/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13/site-packages/glances-4.0.7.dist-info/REQUESTED' ++ wc -l /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-ghost-distinfo ++ cut -f1 '-d ' + lines=1 + '[' 1 -ne 1 ']' + RPM_FILES_ESCAPE=4.19 + /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-files --output-modules /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-modules --buildroot /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT --sitelib /usr/lib/python3.13/site-packages --sitearch /usr/lib64/python3.13/site-packages --python-version 3.13 --pyproject-record /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7-2.mga10.noarch-pyproject-record --prefix /usr glances + install -D -p -m 644 /home/pterjan/rpmbuild/SOURCES/glances.service /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/systemd/system/glances.service + install -D -p -m 644 conf/glances.conf /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/etc/glances/glances.conf + /usr/lib/rpm/check-buildroot + '[' -n '' ']' + /usr/share/spec-helper/clean_files + '[' -n '' ']' + /usr/share/spec-helper/compress_files .xz + '[' -n '' ']' + /usr/share/spec-helper/relink_symlinks + '[' -n '' ']' + /usr/share/spec-helper/clean_perl + '[' -n '' ']' + /usr/share/spec-helper/lib_symlinks + '[' -n '' ']' + /usr/share/spec-helper/gprintify + '[' -n '' ']' + /usr/share/spec-helper/fix_mo + '[' -n '' ']' + /usr/share/spec-helper/fix_pamd + '[' -n '' ']' + /usr/share/spec-helper/remove_info_dir + '[' -n '' ']' + /usr/share/spec-helper/fix_eol + '[' -n '' ']' + /usr/share/spec-helper/check_desktop_files + '[' -n '' ']' + /usr/share/spec-helper/check_elf_files + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-mangle-shebangs *** WARNING: ./usr/lib/python3.13/site-packages/glances/exports/glances_mqtt/__init__.py is executable but has no shebang, removing executable bit + env -u SOURCE_DATE_EPOCH /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j16 Bytecompiling .py files below /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/lib/python3.13 using python3.13 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set + /usr/lib/rpm/redhat/brp-python-hardlink Processing files: glances-4.0.7-2.mga10.noarch Executing(%doc): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.ce4wY0 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + cd glances-4.0.7 + DOCDIR=/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/doc/glances + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/doc/glances + cp -pr /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/AUTHORS /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/doc/glances + cp -pr /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/README.rst /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/doc/glances + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.3q9EnC + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + cd glances-4.0.7 + LICENSEDIR=/home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/licenses/glances + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/licenses/glances + cp -pr /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/glances-4.0.7/COPYING /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT/usr/share/licenses/glances + RPM_EC=0 ++ jobs -p + exit 0 Provides: config(glances) = 4.0.7-2.mga10 glances = 4.0.7-2.mga10 python3.13dist(glances) = 4.0.7 python3dist(glances) = 4.0.7 Requires(interp): /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires(post): /bin/sh Requires(preun): /bin/sh Requires: python(abi) = 3.13 python3.13dist(defusedxml) python3.13dist(packaging) python3.13dist(psutil) >= 5.6.7 python3.13dist(ujson) >= 5.4 Recommends: hddtemp python3-batinfo python3-bottle python3-pysnmp python3-sensors Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build/BUILDROOT Wrote: /home/pterjan/rpmbuild/RPMS/noarch/glances-4.0.7-2.mga10.noarch.rpm Executing(rmbuild): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.Obxf1q + umask 022 + cd /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + test -d /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + rm -rf /home/pterjan/rpmbuild/BUILD/glances-4.0.7-build + RPM_EC=0 ++ jobs -p + exit 0 D: [iurt_root_command] Success!