=>> Building misc/py-powerline-status build started at Wed Jul 8 09:21:57 JST 2026 port directory: /usr/ports/misc/py-powerline-status package name: py312-powerline-status-2.8.4_1 building for: FreeBSD s15amd64-setuptools2-job-04 15.1-STABLE FreeBSD 15.1-STABLE 1501501 amd64 maintained by: bofh@FreeBSD.org Makefile datestamp: -rw-r--r-- 1 root wheel 1529 Apr 13 23:06 /usr/ports/misc/py-powerline-status/Makefile Ports top last git commit: 18628b9022c9c1c0e7cb5e71c2aa1e1e563ca34a Ports top unclean checkout: yes Port dir last git commit: 1c3394560c4f3b7e3e79480f17b767e3a58bd951 Port dir unclean checkout: no Poudriere version: poudriere-git-3.4.8 Host OSVERSION: 1501501 Jail OSVERSION: 1501501 Job Id: 04 ---Begin Environment--- SHELL=/bin/sh OSVERSION=1501501 UNAME_v=FreeBSD 15.1-STABLE 1501501 UNAME_r=15.1-STABLE BLOCKSIZE=K MAIL=/var/mail/root MM_CHARSET=UTF-8 LANG=C.UTF-8 STATUS=1 HOME=/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin MAKE_OBJDIR_CHECK_WRITABLE=0 LOCALBASE=/usr/local USER=root POUDRIERE_NAME=poudriere-git LIBEXECPREFIX=/usr/local/libexec/poudriere POUDRIERE_VERSION=3.4.8 MASTERMNT=/usr/local/poudriere/data/.m/s15amd64-setuptools2/ref LC_COLLATE=C POUDRIERE_BUILD_TYPE=bulk PACKAGE_BUILDING=yes SAVED_TERM=tmux-256color GID=0 OUTPUT_REDIRECTED_STDERR=4 OUTPUT_REDIRECTED=1 UID=0 PWD=/usr/local/poudriere/data/.m/s15amd64-setuptools2/04/.p OUTPUT_REDIRECTED_STDOUT=3 P_PORTS_FEATURES=FLAVORS SUBPACKAGES SELECTED_OPTIONS MASTERNAME=s15amd64-setuptools2 SCRIPTPREFIX=/usr/local/share/poudriere SCRIPTNAME=bulk.sh OLDPWD=/usr/local/poudriere/data/.m/s15amd64-setuptools2/ref/.p/pool POUDRIERE_PKGNAME=poudriere-git-3.4.8 SCRIPTPATH=/usr/local/share/poudriere/bulk.sh POUDRIEREPATH=/usr/local/bin/poudriere ---End Environment--- ---Begin Poudriere Port Flags/Env--- PORT_FLAGS= PKGENV= FLAVOR=py312 MAKE_ARGS= FLAVOR=py312 ---End Poudriere Port Flags/Env--- ---Begin OPTIONS List--- ===> The following configuration options are available for py312-powerline-status-2.8.4_1: DOCS=on: Build and/or install documentation ===> Use 'make config' to modify these settings ---End OPTIONS List--- --MAINTAINER-- bofh@FreeBSD.org --End MAINTAINER-- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- PYTHON="/usr/local/bin/python3.12" XDG_DATA_HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312 XDG_CONFIG_HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312 XDG_CACHE_HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.cache HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312 TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312 XDG_CONFIG_HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312 XDG_CACHE_HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.cache HOME=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312 TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES LDSHARED="cc -shared" PYTHONDONTWRITEBYTECODE= PYTHONOPTIMIZE= PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing " CPP="cpp" CPPFLAGS="" LDFLAGS=" " LIBS="" CXX="c++" CXXFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing " BSD_INSTALL_PROGRAM="install -s -m 555" BSD_INSTALL_LIB="install -s -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" --End MAKE_ENV-- --PLIST_SUB-- PORTDOCS="" PYTHON_INCLUDEDIR=include/python3.12 PYTHON_LIBDIR=lib/python3.12 PYTHON_PLATFORM=freebsd15 PYTHON_SITELIBDIR=lib/python3.12/site-packages PYTHON_SUFFIX=312 PYTHON_BASESUFFIX=312 PYTHON_TAG=.cpython-312 PYTHON_SOABI=.cpython-312 PYTHON_VER=3.12 PYTHON_BASEVER=3.12 PYTHON_VERSION=python3.12 PYTHON2="@comment " PYTHON3="" OSREL=15.1 PREFIX=%D LOCALBASE=/usr/local RESETPREFIX=/usr/local LIB32DIR=lib DOCSDIR="share/doc/powerline-status" EXAMPLESDIR="share/examples/powerline-status" DATADIR="share/powerline-status" WWWDIR="www/powerline-status" ETCDIR="etc/powerline-status" --End PLIST_SUB-- --SUB_LIST-- PYTHON_INCLUDEDIR=/usr/local/include/python3.12 PYTHON_LIBDIR=/usr/local/lib/python3.12 PYTHON_PLATFORM=freebsd15 PYTHON_SITELIBDIR=/usr/local/lib/python3.12/site-packages PYTHON_SUFFIX=312 PYTHON_BASESUFFIX=312 PYTHON_TAG=.cpython-312 PYTHON_SOABI=.cpython-312 PYTHON_VER=3.12 PYTHON_BASEVER=3.12 PYTHON_VERSION=python3.12 PYTHON2="@comment " PYTHON3="" PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/powerline-status DOCSDIR=/usr/local/share/doc/powerline-status EXAMPLESDIR=/usr/local/share/examples/powerline-status WWWDIR=/usr/local/www/powerline-status ETCDIR=/usr/local/etc/powerline-status --End SUB_LIST-- ---Begin make.conf--- USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles OVERLAYS+=/overlays/overlay_setuptools FORCE_PACKAGE=yes PACKAGE_BUILDING=yes PACKAGE_BUILDING_FLAVORS=yes #### #### LICENSES_ACCEPTED= EULA ISC MPEG2ENC DEFAULT_VERSIONS+= magick=7 DEFAULT_VERSIONS+= pgsql=18 DEFAULT_VERSIONS+= samba=4.23 DEFAULT_VERSIONS+= ssl=openssl japanese_fcitx5-mozc_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_UNSET= JAWIKI x11_wm_hikari_SET= INPUTMETHOD GAMMA LAYERSHELL SCREENCOPY VIRTUALINPUT X11 .if $(.CURDIR:M*/x11-wm/hikari) WITH_DEBUG= YES .endif #### #### devel_gamin_set= LIBINOTIFY #### Misc Poudriere #### .include "/etc/make.conf.ports_env" DISABLE_MAKE_JOBS=poudriere ---End make.conf--- --Resource limits-- cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 33554432 stack size (kbytes, -s) 524288 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) unlimited max user processes (-u) 89999 open files (-n) 8192 virtual mem size (kbytes, -v) unlimited swap limit (kbytes, -w) unlimited socket buffer size (bytes, -b) unlimited pseudo-terminals (-p) unlimited kqueues (-k) unlimited umtx shared locks (-o) unlimited pipebuf (kbytes, -y) unlimited --End resource limits-- =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> License MIT accepted by the user =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py312-powerline-status-2.8.4_1 depends on file: /usr/local/sbin/pkg - not found ===> Installing existing package /packages/All/pkg-2.7.5.pkg [s15amd64-setuptools2-job-04] Installing pkg-2.7.5... [s15amd64-setuptools2-job-04] Extracting pkg-2.7.5: .......... done ===> py312-powerline-status-2.8.4_1 depends on file: /usr/local/sbin/pkg - found ===> Returning to build of py312-powerline-status-2.8.4_1 =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 ===> License MIT accepted by the user ===> Fetching all distfiles required by py312-powerline-status-2.8.4_1 for building =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 ===> License MIT accepted by the user ===> Fetching all distfiles required by py312-powerline-status-2.8.4_1 for building => SHA256 Checksum OK for powerline-powerline-2.8.4_GH0.tar.gz. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> License MIT accepted by the user ===> Fetching all distfiles required by py312-powerline-status-2.8.4_1 for building ===> Extracting for py312-powerline-status-2.8.4_1 => SHA256 Checksum OK for powerline-powerline-2.8.4_GH0.tar.gz. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Patching for py312-powerline-status-2.8.4_1 ===> Applying FreeBSD patches for py312-powerline-status-2.8.4_1 from /usr/ports/misc/py-powerline-status/files =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py312-powerline-status-2.8.4_1 depends on package: py312-sphinx>=0,1 - not found ===> Installing existing package /packages/All/py312-sphinx-9.0.4,1.pkg [s15amd64-setuptools2-job-04] Installing py312-sphinx-9.0.4,1... [s15amd64-setuptools2-job-04] `-- Installing ca_root_nss-3.124... [s15amd64-setuptools2-job-04] `-- Extracting ca_root_nss-3.124: ..... done [s15amd64-setuptools2-job-04] `-- Installing py312-Babel-2.18.0... [s15amd64-setuptools2-job-04] | `-- Installing python312-3.12.13_3... [s15amd64-setuptools2-job-04] | | `-- Installing expat-2.8.2... [s15amd64-setuptools2-job-04] | | `-- Extracting expat-2.8.2: .......... done [s15amd64-setuptools2-job-04] | | `-- Installing gettext-runtime-1.0_1... [s15amd64-setuptools2-job-04] | | `-- Installing indexinfo-0.3.1_1... [s15amd64-setuptools2-job-04] | | `-- Extracting indexinfo-0.3.1_1: .... done [s15amd64-setuptools2-job-04] | | `-- Extracting gettext-runtime-1.0_1: .......... done [s15amd64-setuptools2-job-04] | | `-- Installing libffi-3.6.0... [s15amd64-setuptools2-job-04] | | `-- Extracting libffi-3.6.0: .......... done [s15amd64-setuptools2-job-04] | | `-- Installing mpdecimal-4.0.1... [s15amd64-setuptools2-job-04] | | `-- Extracting mpdecimal-4.0.1: .......... done [s15amd64-setuptools2-job-04] | | `-- Installing openssl-3.0.21,1... [s15amd64-setuptools2-job-04] | | `-- Extracting openssl-3.0.21,1: .......... done [s15amd64-setuptools2-job-04] | | `-- Installing readline-8.3.3... [s15amd64-setuptools2-job-04] | | `-- Extracting readline-8.3.3: .......... done [s15amd64-setuptools2-job-04] | `-- Extracting python312-3.12.13_3: .......... done [s15amd64-setuptools2-job-04] `-- Extracting py312-Babel-2.18.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-Jinja2-3.1.6... [s15amd64-setuptools2-job-04] | `-- Installing py312-markupsafe-3.0.3... [s15amd64-setuptools2-job-04] | `-- Extracting py312-markupsafe-3.0.3: .......... done [s15amd64-setuptools2-job-04] `-- Extracting py312-Jinja2-3.1.6: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-alabaster-0.7.16... [s15amd64-setuptools2-job-04] `-- Extracting py312-alabaster-0.7.16: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-docutils-0.21.2,1... [s15amd64-setuptools2-job-04] `-- Extracting py312-docutils-0.21.2,1: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-imagesize-2.0.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-imagesize-2.0.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-packaging-26.2... [s15amd64-setuptools2-job-04] `-- Extracting py312-packaging-26.2: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-pygments-2.20.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-pygments-2.20.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-requests-2.34.2... [s15amd64-setuptools2-job-04] | `-- Installing py312-certifi-2026.5.20... [s15amd64-setuptools2-job-04] | `-- Extracting py312-certifi-2026.5.20: .......... done [s15amd64-setuptools2-job-04] | `-- Installing py312-charset-normalizer-3.4.7... [s15amd64-setuptools2-job-04] | `-- Extracting py312-charset-normalizer-3.4.7: .......... done [s15amd64-setuptools2-job-04] | `-- Installing py312-idna-3.18... [s15amd64-setuptools2-job-04] | `-- Extracting py312-idna-3.18: .......... done [s15amd64-setuptools2-job-04] | `-- Installing py312-pysocks-1.7.1_1... [s15amd64-setuptools2-job-04] | `-- Extracting py312-pysocks-1.7.1_1: .......... done [s15amd64-setuptools2-job-04] | `-- Installing py312-urllib3-2.7.0,1... [s15amd64-setuptools2-job-04] | `-- Extracting py312-urllib3-2.7.0,1: .......... done [s15amd64-setuptools2-job-04] `-- Extracting py312-requests-2.34.2: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-roman-numerals-4.1.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-roman-numerals-4.1.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-snowballstemmer-3.1.0... [s15amd64-setuptools2-job-04] | `-- Installing py312-pystemmer-2.0.1_1... [s15amd64-setuptools2-job-04] | `-- Extracting py312-pystemmer-2.0.1_1: ......... done [s15amd64-setuptools2-job-04] `-- Extracting py312-snowballstemmer-3.1.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-applehelp-2.0.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-applehelp-2.0.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-devhelp-2.0.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-devhelp-2.0.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-htmlhelp-2.1.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-htmlhelp-2.1.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-jsmath-1.0.1_1... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-jsmath-1.0.1_1: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-qthelp-2.0.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-qthelp-2.0.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-serializinghtml-2.0.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-serializinghtml-2.0.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-typing-extensions-4.15.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-typing-extensions-4.15.0: .......... done [s15amd64-setuptools2-job-04] Extracting py312-sphinx-9.0.4,1: .......... done ===== Message from ca_root_nss-3.124: -- FreeBSD does not, and can not warrant that the certification authorities whose certificates are included in this package have in any way been audited for trustworthiness or RFC 3647 compliance. Assessment and verification of trust is the complete responsibility of the system administrator. This package installs symlinks to support root certificate discovery for software that either uses other cryptographic libraries than OpenSSL, or use OpenSSL but do not follow recommended practice. If you prefer to do this manually, replace the following symlinks with either an empty file or your site-local certificate bundle. * /etc/ssl/cert.pem * /usr/local/etc/ssl/cert.pem * /usr/local/openssl/cert.pem ===== Message from openssl-3.0.21,1: -- This port (security/openssl) will update from 3.0 to 3.5 per 2026-07-01 (2026Q3) in anticipation of the End-of-Life of OpenSSL 3.0. A new port (security/openssl30) will be created for the remainder of the lifespan of OpenSSL 3.0 and FreeBSD 14. See: https://openssl-library.org/roadmap/index.html ===== Message from python312-3.12.13_3: -- Note that some standard Python modules are provided as separate ports as they require additional dependencies. They are available as: py312-gdbm databases/py-gdbm@py312 py312-sqlite3 databases/py-sqlite3@py312 py312-tkinter x11-toolkits/py-tkinter@py312 ===== Message from py312-urllib3-2.7.0,1: -- Since version 1.25 HTTPS connections are now verified by default which is done via "cert_reqs = 'CERT_REQUIRED'". While certificate verification can be disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to leave it on. Various consumers of net/py-urllib3 already have implemented routines that either explicitly enable or disable HTTPS certificate verification (e.g. via configuration settings, CLI arguments, etc.). Yet it may happen that there are still some consumers which don't explicitly enable/disable certificate verification for HTTPS connections which could then lead to errors (as is often the case with self-signed certificates). In case of an error one should try first to temporarily disable certificate verification of the problematic urllib3 consumer to see if that approach will remedy the issue. ===> py312-powerline-status-2.8.4_1 depends on package: py312-sphinx>=0,1 - found ===> Returning to build of py312-powerline-status-2.8.4_1 ===> py312-powerline-status-2.8.4_1 depends on package: py312-sphinx_rtd_theme>=0 - not found ===> Installing existing package /packages/All/py312-sphinx_rtd_theme-3.1.0.pkg [s15amd64-setuptools2-job-04] Installing py312-sphinx_rtd_theme-3.1.0... [s15amd64-setuptools2-job-04] `-- Installing py312-sphinxcontrib-jquery-4.1... [s15amd64-setuptools2-job-04] `-- Extracting py312-sphinxcontrib-jquery-4.1: .......... done [s15amd64-setuptools2-job-04] Extracting py312-sphinx_rtd_theme-3.1.0: .......... done ===> py312-powerline-status-2.8.4_1 depends on package: py312-sphinx_rtd_theme>=0 - found ===> Returning to build of py312-powerline-status-2.8.4_1 ===> py312-powerline-status-2.8.4_1 depends on package: py312-setuptools>=63.1.0 - not found ===> Installing existing package /packages/All/py312-setuptools-81.0.0.pkg [s15amd64-setuptools2-job-04] Installing py312-setuptools-81.0.0... [s15amd64-setuptools2-job-04] `-- Installing py312-more-itertools-11.1.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-more-itertools-11.1.0: .......... done [s15amd64-setuptools2-job-04] `-- Installing py312-wheel-0.47.0... [s15amd64-setuptools2-job-04] `-- Extracting py312-wheel-0.47.0: .......... done [s15amd64-setuptools2-job-04] Extracting py312-setuptools-81.0.0: .......... done ===> py312-powerline-status-2.8.4_1 depends on package: py312-setuptools>=63.1.0 - found ===> Returning to build of py312-powerline-status-2.8.4_1 ===> py312-powerline-status-2.8.4_1 depends on file: /usr/local/bin/python3.12 - found =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Configuring for py312-powerline-status-2.8.4_1 /usr/local/lib/python3.12/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/local/lib/python3.12/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running config =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Building for py312-powerline-status-2.8.4_1 /usr/local/lib/python3.12/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/local/lib/python3.12/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running build running build_py creating build/lib/powerline copying powerline/ipython.py -> build/lib/powerline copying powerline/segment.py -> build/lib/powerline copying powerline/shell.py -> build/lib/powerline copying powerline/__init__.py -> build/lib/powerline copying powerline/version.py -> build/lib/powerline copying powerline/colorscheme.py -> build/lib/powerline copying powerline/vim.py -> build/lib/powerline copying powerline/pdb.py -> build/lib/powerline copying powerline/renderer.py -> build/lib/powerline copying powerline/config.py -> build/lib/powerline copying powerline/theme.py -> build/lib/powerline copying powerline/lemonbar.py -> build/lib/powerline creating build/lib/powerline/renderers copying powerline/renderers/__init__.py -> build/lib/powerline/renderers copying powerline/renderers/i3bar.py -> build/lib/powerline/renderers copying powerline/renderers/vim.py -> build/lib/powerline/renderers copying powerline/renderers/pdb.py -> build/lib/powerline/renderers copying powerline/renderers/tmux.py -> build/lib/powerline/renderers copying powerline/renderers/lemonbar.py -> build/lib/powerline/renderers copying powerline/renderers/pango_markup.py -> build/lib/powerline/renderers creating build/lib/powerline/matchers copying powerline/matchers/__init__.py -> build/lib/powerline/matchers creating build/lib/powerline/lint copying powerline/lint/context.py -> build/lib/powerline/lint copying powerline/lint/checks.py -> build/lib/powerline/lint copying powerline/lint/imp.py -> build/lib/powerline/lint copying powerline/lint/__init__.py -> build/lib/powerline/lint copying powerline/lint/spec.py -> build/lib/powerline/lint copying powerline/lint/inspect.py -> build/lib/powerline/lint copying powerline/lint/selfcheck.py -> build/lib/powerline/lint creating build/lib/powerline/lib copying powerline/lib/memoize.py -> build/lib/powerline/lib copying powerline/lib/encoding.py -> build/lib/powerline/lib copying powerline/lib/inotify.py -> build/lib/powerline/lib copying powerline/lib/shell.py -> build/lib/powerline/lib copying powerline/lib/debug.py -> build/lib/powerline/lib copying powerline/lib/__init__.py -> build/lib/powerline/lib copying powerline/lib/dict.py -> build/lib/powerline/lib copying powerline/lib/overrides.py -> build/lib/powerline/lib copying powerline/lib/path.py -> build/lib/powerline/lib copying powerline/lib/threaded.py -> build/lib/powerline/lib copying powerline/lib/config.py -> build/lib/powerline/lib copying powerline/lib/monotonic.py -> build/lib/powerline/lib copying powerline/lib/url.py -> build/lib/powerline/lib copying powerline/lib/humanize_bytes.py -> build/lib/powerline/lib copying powerline/lib/unicode.py -> build/lib/powerline/lib creating build/lib/powerline/segments copying powerline/segments/ipython.py -> build/lib/powerline/segments copying powerline/segments/shell.py -> build/lib/powerline/segments copying powerline/segments/__init__.py -> build/lib/powerline/segments copying powerline/segments/pdb.py -> build/lib/powerline/segments copying powerline/segments/i3wm.py -> build/lib/powerline/segments copying powerline/segments/tmux.py -> build/lib/powerline/segments creating build/lib/powerline/listers copying powerline/listers/__init__.py -> build/lib/powerline/listers copying powerline/listers/vim.py -> build/lib/powerline/listers copying powerline/listers/pdb.py -> build/lib/powerline/listers copying powerline/listers/i3wm.py -> build/lib/powerline/listers creating build/lib/powerline/commands copying powerline/commands/main.py -> build/lib/powerline/commands copying powerline/commands/daemon.py -> build/lib/powerline/commands copying powerline/commands/__init__.py -> build/lib/powerline/commands copying powerline/commands/config.py -> build/lib/powerline/commands copying powerline/commands/lint.py -> build/lib/powerline/commands copying powerline/commands/lemonbar.py -> build/lib/powerline/commands creating build/lib/powerline/selectors copying powerline/selectors/__init__.py -> build/lib/powerline/selectors copying powerline/selectors/vim.py -> build/lib/powerline/selectors creating build/lib/powerline/bindings copying powerline/bindings/__init__.py -> build/lib/powerline/bindings copying powerline/bindings/config.py -> build/lib/powerline/bindings creating build/lib/powerline/renderers/shell copying powerline/renderers/shell/__init__.py -> build/lib/powerline/renderers/shell copying powerline/renderers/shell/bash.py -> build/lib/powerline/renderers/shell copying powerline/renderers/shell/readline.py -> build/lib/powerline/renderers/shell copying powerline/renderers/shell/ksh.py -> build/lib/powerline/renderers/shell copying powerline/renderers/shell/zsh.py -> build/lib/powerline/renderers/shell copying powerline/renderers/shell/tcsh.py -> build/lib/powerline/renderers/shell copying powerline/renderers/shell/rcsh.py -> build/lib/powerline/renderers/shell creating build/lib/powerline/renderers/ipython copying powerline/renderers/ipython/since_7.py -> build/lib/powerline/renderers/ipython copying powerline/renderers/ipython/pre_5.py -> build/lib/powerline/renderers/ipython copying powerline/renderers/ipython/__init__.py -> build/lib/powerline/renderers/ipython copying powerline/renderers/ipython/since_5.py -> build/lib/powerline/renderers/ipython creating build/lib/powerline/matchers/vim copying powerline/matchers/vim/__init__.py -> build/lib/powerline/matchers/vim creating build/lib/powerline/matchers/vim/plugin copying powerline/matchers/vim/plugin/__init__.py -> build/lib/powerline/matchers/vim/plugin copying powerline/matchers/vim/plugin/nerdtree.py -> build/lib/powerline/matchers/vim/plugin copying powerline/matchers/vim/plugin/gundo.py -> build/lib/powerline/matchers/vim/plugin copying powerline/matchers/vim/plugin/commandt.py -> build/lib/powerline/matchers/vim/plugin creating build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/nodes.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/loader.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/reader.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/__init__.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/events.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/tokens.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/composer.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/markedvalue.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/resolver.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/scanner.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/parser.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/error.py -> build/lib/powerline/lint/markedjson copying powerline/lint/markedjson/constructor.py -> build/lib/powerline/lint/markedjson creating build/lib/powerline/lib/watcher copying powerline/lib/watcher/tree.py -> build/lib/powerline/lib/watcher copying powerline/lib/watcher/inotify.py -> build/lib/powerline/lib/watcher copying powerline/lib/watcher/__init__.py -> build/lib/powerline/lib/watcher copying powerline/lib/watcher/stat.py -> build/lib/powerline/lib/watcher copying powerline/lib/watcher/uv.py -> build/lib/powerline/lib/watcher creating build/lib/powerline/lib/vcs copying powerline/lib/vcs/bzr.py -> build/lib/powerline/lib/vcs copying powerline/lib/vcs/__init__.py -> build/lib/powerline/lib/vcs copying powerline/lib/vcs/git.py -> build/lib/powerline/lib/vcs copying powerline/lib/vcs/mercurial.py -> build/lib/powerline/lib/vcs creating build/lib/powerline/segments/common copying powerline/segments/common/net.py -> build/lib/powerline/segments/common copying powerline/segments/common/__init__.py -> build/lib/powerline/segments/common copying powerline/segments/common/mail.py -> build/lib/powerline/segments/common copying powerline/segments/common/bat.py -> build/lib/powerline/segments/common copying powerline/segments/common/players.py -> build/lib/powerline/segments/common copying powerline/segments/common/sys.py -> build/lib/powerline/segments/common copying powerline/segments/common/time.py -> build/lib/powerline/segments/common copying powerline/segments/common/wthr.py -> build/lib/powerline/segments/common copying powerline/segments/common/env.py -> build/lib/powerline/segments/common copying powerline/segments/common/vcs.py -> build/lib/powerline/segments/common creating build/lib/powerline/segments/vim copying powerline/segments/vim/__init__.py -> build/lib/powerline/segments/vim creating build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/syntastic.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/__init__.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/ale.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/coc.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/nerdtree.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/commandt.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/capslock.py -> build/lib/powerline/segments/vim/plugin copying powerline/segments/vim/plugin/tagbar.py -> build/lib/powerline/segments/vim/plugin creating build/lib/powerline/bindings/zsh copying powerline/bindings/zsh/__init__.py -> build/lib/powerline/bindings/zsh creating build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/__init__.py -> build/lib/powerline/bindings/tmux creating build/lib/powerline/bindings/qtile copying powerline/bindings/qtile/widget.py -> build/lib/powerline/bindings/qtile copying powerline/bindings/qtile/__init__.py -> build/lib/powerline/bindings/qtile creating build/lib/powerline/bindings/wm copying powerline/bindings/wm/__init__.py -> build/lib/powerline/bindings/wm copying powerline/bindings/wm/awesome.py -> build/lib/powerline/bindings/wm creating build/lib/powerline/bindings/ipython copying powerline/bindings/ipython/since_7.py -> build/lib/powerline/bindings/ipython copying powerline/bindings/ipython/__init__.py -> build/lib/powerline/bindings/ipython copying powerline/bindings/ipython/post_0_11.py -> build/lib/powerline/bindings/ipython copying powerline/bindings/ipython/pre_0_11.py -> build/lib/powerline/bindings/ipython copying powerline/bindings/ipython/since_5.py -> build/lib/powerline/bindings/ipython creating build/lib/powerline/bindings/pdb copying powerline/bindings/pdb/__main__.py -> build/lib/powerline/bindings/pdb copying powerline/bindings/pdb/__init__.py -> build/lib/powerline/bindings/pdb creating build/lib/powerline/bindings/vim copying powerline/bindings/vim/__init__.py -> build/lib/powerline/bindings/vim running egg_info creating powerline_status.egg-info writing powerline_status.egg-info/PKG-INFO writing dependency_links to powerline_status.egg-info/dependency_links.txt writing requirements to powerline_status.egg-info/requires.txt writing top-level names to powerline_status.egg-info/top_level.txt writing manifest file 'powerline_status.egg-info/SOURCES.txt' reading manifest file 'powerline_status.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.pyc' found under directory 'powerline/bindings' warning: no previously-included files matching '*.pyo' found under directory 'powerline/bindings' adding license file 'LICENSE' writing manifest file 'powerline_status.egg-info/SOURCES.txt' /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.awesome' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.awesome' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.awesome' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.awesome' to be distributed and are already explicitly excluding 'powerline.bindings.awesome' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.bar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.bar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.bar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.bar' to be distributed and are already explicitly excluding 'powerline.bindings.bar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.bash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.bash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.bash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.bash' to be distributed and are already explicitly excluding 'powerline.bindings.bash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.fish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.fish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.fish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.fish' to be distributed and are already explicitly excluding 'powerline.bindings.fish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.i3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.i3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.i3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.i3' to be distributed and are already explicitly excluding 'powerline.bindings.i3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.lemonbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.lemonbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.lemonbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.lemonbar' to be distributed and are already explicitly excluding 'powerline.bindings.lemonbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.rc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.rc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.rc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.rc' to be distributed and are already explicitly excluding 'powerline.bindings.rc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.shell' to be distributed and are already explicitly excluding 'powerline.bindings.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.tcsh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.tcsh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.tcsh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.tcsh' to be distributed and are already explicitly excluding 'powerline.bindings.tcsh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.vim.autoload.powerline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.vim.autoload.powerline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.vim.autoload.powerline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.vim.autoload.powerline' to be distributed and are already explicitly excluding 'powerline.bindings.vim.autoload.powerline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.vim.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.vim.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 'powerline.bindings.vim.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 'powerline.bindings.vim.plugin' to be distributed and are already explicitly excluding 'powerline.bindings.vim.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/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files' to be distributed and are already explicitly excluding 'powerline.config_files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.ipython' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.ipython' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.ipython' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.ipython' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.ipython' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.pdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.pdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.pdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.pdb' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.pdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.shell' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.tmux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.tmux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.tmux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.tmux' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.tmux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.vim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.vim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.vim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.vim' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.vim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes' to be distributed and are already explicitly excluding 'powerline.config_files.themes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.ipython' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.ipython' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.ipython' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.ipython' to be distributed and are already explicitly excluding 'powerline.config_files.themes.ipython' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.pdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.pdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.pdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.pdb' to be distributed and are already explicitly excluding 'powerline.config_files.themes.pdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.shell' to be distributed and are already explicitly excluding 'powerline.config_files.themes.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.tmux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.tmux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.tmux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.tmux' to be distributed and are already explicitly excluding 'powerline.config_files.themes.tmux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.vim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.vim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.vim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.vim' to be distributed and are already explicitly excluding 'powerline.config_files.themes.vim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.wm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.wm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.wm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.wm' to be distributed and are already explicitly excluding 'powerline.config_files.themes.wm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.dist.systemd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.dist.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 'powerline.dist.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 'powerline.dist.systemd' to be distributed and are already explicitly excluding 'powerline.dist.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) creating build/lib/powerline/config_files copying powerline/config_files/colors.json -> build/lib/powerline/config_files copying powerline/config_files/config.json -> build/lib/powerline/config_files creating build/lib/powerline/config_files/colorschemes copying powerline/config_files/colorschemes/default.json -> build/lib/powerline/config_files/colorschemes copying powerline/config_files/colorschemes/solarized.json -> build/lib/powerline/config_files/colorschemes creating build/lib/powerline/config_files/colorschemes/ipython copying powerline/config_files/colorschemes/ipython/__main__.json -> build/lib/powerline/config_files/colorschemes/ipython creating build/lib/powerline/config_files/colorschemes/pdb copying powerline/config_files/colorschemes/pdb/__main__.json -> build/lib/powerline/config_files/colorschemes/pdb copying powerline/config_files/colorschemes/pdb/default.json -> build/lib/powerline/config_files/colorschemes/pdb copying powerline/config_files/colorschemes/pdb/solarized.json -> build/lib/powerline/config_files/colorschemes/pdb creating build/lib/powerline/config_files/colorschemes/shell copying powerline/config_files/colorschemes/shell/__main__.json -> build/lib/powerline/config_files/colorschemes/shell copying powerline/config_files/colorschemes/shell/default.json -> build/lib/powerline/config_files/colorschemes/shell copying powerline/config_files/colorschemes/shell/solarized.json -> build/lib/powerline/config_files/colorschemes/shell creating build/lib/powerline/config_files/colorschemes/tmux copying powerline/config_files/colorschemes/tmux/default.json -> build/lib/powerline/config_files/colorschemes/tmux copying powerline/config_files/colorschemes/tmux/solarized.json -> build/lib/powerline/config_files/colorschemes/tmux creating build/lib/powerline/config_files/colorschemes/vim copying powerline/config_files/colorschemes/vim/__main__.json -> build/lib/powerline/config_files/colorschemes/vim copying powerline/config_files/colorschemes/vim/default.json -> build/lib/powerline/config_files/colorschemes/vim copying powerline/config_files/colorschemes/vim/solarized.json -> build/lib/powerline/config_files/colorschemes/vim copying powerline/config_files/colorschemes/vim/solarizedlight.json -> build/lib/powerline/config_files/colorschemes/vim creating build/lib/powerline/config_files/themes copying powerline/config_files/themes/ascii.json -> build/lib/powerline/config_files/themes copying powerline/config_files/themes/powerline.json -> build/lib/powerline/config_files/themes copying powerline/config_files/themes/powerline_terminus.json -> build/lib/powerline/config_files/themes copying powerline/config_files/themes/powerline_unicode7.json -> build/lib/powerline/config_files/themes copying powerline/config_files/themes/unicode.json -> build/lib/powerline/config_files/themes copying powerline/config_files/themes/unicode_terminus.json -> build/lib/powerline/config_files/themes copying powerline/config_files/themes/unicode_terminus_condensed.json -> build/lib/powerline/config_files/themes creating build/lib/powerline/config_files/themes/ipython copying powerline/config_files/themes/ipython/in.json -> build/lib/powerline/config_files/themes/ipython copying powerline/config_files/themes/ipython/in2.json -> build/lib/powerline/config_files/themes/ipython copying powerline/config_files/themes/ipython/out.json -> build/lib/powerline/config_files/themes/ipython copying powerline/config_files/themes/ipython/rewrite.json -> build/lib/powerline/config_files/themes/ipython creating build/lib/powerline/config_files/themes/pdb copying powerline/config_files/themes/pdb/default.json -> build/lib/powerline/config_files/themes/pdb creating build/lib/powerline/config_files/themes/shell copying powerline/config_files/themes/shell/__main__.json -> build/lib/powerline/config_files/themes/shell copying powerline/config_files/themes/shell/continuation.json -> build/lib/powerline/config_files/themes/shell copying powerline/config_files/themes/shell/default.json -> build/lib/powerline/config_files/themes/shell copying powerline/config_files/themes/shell/default_leftonly.json -> build/lib/powerline/config_files/themes/shell copying powerline/config_files/themes/shell/select.json -> build/lib/powerline/config_files/themes/shell creating build/lib/powerline/config_files/themes/tmux copying powerline/config_files/themes/tmux/default.json -> build/lib/powerline/config_files/themes/tmux creating build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/__main__.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/cmdwin.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/default.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/help.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/plugin_commandt.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/plugin_gundo-preview.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/plugin_gundo.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/plugin_nerdtree.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/quickfix.json -> build/lib/powerline/config_files/themes/vim copying powerline/config_files/themes/vim/tabline.json -> build/lib/powerline/config_files/themes/vim creating build/lib/powerline/config_files/themes/wm copying powerline/config_files/themes/wm/default.json -> build/lib/powerline/config_files/themes/wm creating build/lib/powerline/dist/systemd copying powerline/dist/systemd/powerline-daemon.service -> build/lib/powerline/dist/systemd creating build/lib/powerline/bindings/awesome copying powerline/bindings/awesome/powerline-awesome.py -> build/lib/powerline/bindings/awesome copying powerline/bindings/awesome/powerline.lua -> build/lib/powerline/bindings/awesome creating build/lib/powerline/bindings/bar copying powerline/bindings/bar/powerline-bar.py -> build/lib/powerline/bindings/bar creating build/lib/powerline/bindings/bash copying powerline/bindings/bash/powerline.sh -> build/lib/powerline/bindings/bash creating build/lib/powerline/bindings/fish copying powerline/bindings/fish/powerline-setup.fish -> build/lib/powerline/bindings/fish creating build/lib/powerline/bindings/i3 copying powerline/bindings/i3/powerline-i3.py -> build/lib/powerline/bindings/i3 creating build/lib/powerline/bindings/lemonbar copying powerline/bindings/lemonbar/powerline-lemonbar.py -> build/lib/powerline/bindings/lemonbar creating build/lib/powerline/bindings/rc copying powerline/bindings/rc/powerline.rc -> build/lib/powerline/bindings/rc creating build/lib/powerline/bindings/shell copying powerline/bindings/shell/powerline.sh -> build/lib/powerline/bindings/shell creating build/lib/powerline/bindings/tcsh copying powerline/bindings/tcsh/powerline.tcsh -> build/lib/powerline/bindings/tcsh copying powerline/bindings/zsh/powerline.zsh -> build/lib/powerline/bindings/zsh copying powerline/bindings/tmux/powerline-base.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline_tmux_1.7_plus.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline_tmux_1.8.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline_tmux_1.8_minus.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline_tmux_1.8_plus.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline_tmux_1.9_plus.conf -> build/lib/powerline/bindings/tmux copying powerline/bindings/tmux/powerline_tmux_2.1_plus.conf -> build/lib/powerline/bindings/tmux creating build/lib/powerline/bindings/vim/autoload/powerline copying powerline/bindings/vim/autoload/powerline/debug.vim -> build/lib/powerline/bindings/vim/autoload/powerline creating build/lib/powerline/bindings/vim/plugin copying powerline/bindings/vim/plugin/powerline.vim -> build/lib/powerline/bindings/vim/plugin running build_scripts creating build/scripts-3.12 copying and adjusting scripts/powerline-lint -> build/scripts-3.12 copying and adjusting scripts/powerline-daemon -> build/scripts-3.12 copying and adjusting scripts/powerline-render -> build/scripts-3.12 copying and adjusting scripts/powerline-config -> build/scripts-3.12 changing mode of build/scripts-3.12/powerline-lint from 644 to 755 changing mode of build/scripts-3.12/powerline-daemon from 644 to 755 changing mode of build/scripts-3.12/powerline-render from 644 to 755 changing mode of build/scripts-3.12/powerline-config from 644 to 755 sphinx-build-3.12 -b man -T -d _build/doctrees source _build/man Running Sphinx v9.0.4 WARNING: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code. loading translations [en]... done making output directory... done WARNING: directive 'autofunction' is already registered and will not be overridden [app.add_directive] WARNING: directive 'autoattribute' is already registered and will not be overridden [app.add_directive] Converting `source_suffix = '.rst'` to `source_suffix = {'.rst': 'restructuredtext'}`. building [mo]: targets for 0 po files that are out of date writing output... building [man]: all manpages updating environment: [new config] 38 added, 0 changed, 0 removed reading sources... [ 3%] commands reading sources... [ 5%] commands/config reading sources... [ 8%] commands/daemon reading sources... [ 11%] commands/lint reading sources... [ 13%] commands/main reading sources... [ 16%] configuration reading sources... [ 18%] configuration/listers reading sources... [ 21%] configuration/local reading sources... [ 24%] configuration/reference reading sources... [ 26%] configuration/segments reading sources... [ 29%] configuration/segments/common reading sources... [ 32%] configuration/segments/i3wm reading sources... [ 34%] configuration/segments/pdb reading sources... [ 37%] configuration/segments/shell reading sources... [ 39%] configuration/segments/tmux reading sources... [ 42%] configuration/segments/vim reading sources... [ 45%] configuration/selectors reading sources... [ 47%] configuration/selectors/vim reading sources... [ 50%] develop reading sources... [ 53%] develop/extensions reading sources... [ 55%] develop/listers reading sources... [ 58%] develop/local-themes reading sources... [ 61%] develop/segments reading sources... [ 63%] develop/tips-and-tricks reading sources... [ 66%] index reading sources... [ 68%] installation reading sources... [ 71%] installation/linux reading sources... [ 74%] installation/osx reading sources... [ 76%] license-and-credits reading sources... [ 79%] overview reading sources... [ 82%] tips-and-tricks reading sources... [ 84%] troubleshooting reading sources... [ 87%] troubleshooting/linux reading sources... [ 89%] troubleshooting/osx reading sources... [ 92%] usage reading sources... [ 95%] usage/other reading sources... [ 97%] usage/shell-prompts reading sources... [100%] usage/wm-widgets /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/powerline/segments/common/env.py:docstring of powerline.segments.common.env.virtualenv:3: ERROR: Unexpected indentation. [docutils] /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/powerline/segments/common/env.py:docstring of powerline.segments.common.env.virtualenv:4: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils] /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/source/develop/segments.rst:534: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils] looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done copying assets... copying assets: done writing... powerline.1 { } powerline-config.1 { } powerline-lint.1 { } powerline-daemon.1 { } done build succeeded, 6 warnings. The manual pages are in _build/man. Build finished. The manual pages are in _build/man. sphinx-build-3.12 -b html -T -d _build/doctrees source _build/html Running Sphinx v9.0.4 WARNING: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code. loading translations [en]... done making output directory... done WARNING: directive 'autofunction' is already registered and will not be overridden [app.add_directive] WARNING: directive 'autoattribute' is already registered and will not be overridden [app.add_directive] Converting `source_suffix = '.rst'` to `source_suffix = {'.rst': 'restructuredtext'}`. loading pickled environment... done building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 38 source files that are out of date updating environment: 0 added, 0 changed, 0 removed reading sources... looking for now-outdated files... none found preparing documents... done copying assets... copying static files... Writing evaluated template result to /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/html/_static/documentation_options.js Writing evaluated template result to /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/html/_static/language_data.js Writing evaluated template result to /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/html/_static/basic.css Writing evaluated template result to /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/html/_static/js/versions.js copying static files: done copying extra files... copying extra files: done copying assets: done writing output... [ 3%] commands writing output... [ 5%] commands/config writing output... [ 8%] commands/daemon writing output... [ 11%] commands/lint writing output... [ 13%] commands/main writing output... [ 16%] configuration writing output... [ 18%] configuration/listers writing output... [ 21%] configuration/local writing output... [ 24%] configuration/reference writing output... [ 26%] configuration/segments writing output... [ 29%] configuration/segments/common writing output... [ 32%] configuration/segments/i3wm writing output... [ 34%] configuration/segments/pdb writing output... [ 37%] configuration/segments/shell writing output... [ 39%] configuration/segments/tmux writing output... [ 42%] configuration/segments/vim writing output... [ 45%] configuration/selectors writing output... [ 47%] configuration/selectors/vim writing output... [ 50%] develop writing output... [ 53%] develop/extensions writing output... [ 55%] develop/listers writing output... [ 58%] develop/local-themes writing output... [ 61%] develop/segments writing output... [ 63%] develop/tips-and-tricks writing output... [ 66%] index writing output... [ 68%] installation writing output... [ 71%] installation/linux writing output... [ 74%] installation/osx writing output... [ 76%] license-and-credits writing output... [ 79%] overview writing output... [ 82%] tips-and-tricks writing output... [ 84%] troubleshooting writing output... [ 87%] troubleshooting/linux writing output... [ 89%] troubleshooting/osx writing output... [ 92%] usage writing output... [ 95%] usage/other writing output... [ 97%] usage/shell-prompts writing output... [100%] usage/wm-widgets generating indices... genindex py-modindex done highlighting module code... [ 3%] _io highlighting module code... [ 7%] powerline highlighting module code... [ 10%] powerline.listers.i3wm highlighting module code... [ 14%] powerline.listers.pdb highlighting module code... [ 17%] powerline.listers.vim highlighting module code... [ 21%] powerline.renderer highlighting module code... [ 24%] powerline.segments highlighting module code... [ 28%] powerline.segments.common.bat highlighting module code... [ 31%] powerline.segments.common.env highlighting module code... [ 34%] powerline.segments.common.mail highlighting module code... [ 38%] powerline.segments.common.net highlighting module code... [ 41%] powerline.segments.common.players highlighting module code... [ 45%] powerline.segments.common.sys highlighting module code... [ 48%] powerline.segments.common.time highlighting module code... [ 52%] powerline.segments.common.vcs highlighting module code... [ 55%] powerline.segments.common.wthr highlighting module code... [ 59%] powerline.segments.i3wm highlighting module code... [ 62%] powerline.segments.pdb highlighting module code... [ 66%] powerline.segments.shell highlighting module code... [ 69%] powerline.segments.tmux highlighting module code... [ 72%] powerline.segments.vim highlighting module code... [ 76%] powerline.segments.vim.plugin.ale highlighting module code... [ 79%] powerline.segments.vim.plugin.capslock highlighting module code... [ 83%] powerline.segments.vim.plugin.commandt highlighting module code... [ 86%] powerline.segments.vim.plugin.nerdtree highlighting module code... [ 90%] powerline.segments.vim.plugin.syntastic highlighting module code... [ 93%] powerline.segments.vim.plugin.tagbar highlighting module code... [ 97%] powerline.selectors.vim highlighting module code... [100%] powerline.vim writing additional pages... search done copying images... [ 10%] _static/img/pl-mode-normal.png copying images... [ 20%] _static/img/pl-mode-insert.png copying images... [ 30%] _static/img/pl-mode-visual.png copying images... [ 40%] _static/img/pl-mode-replace.png copying images... [ 50%] _static/img/pl-truncate1.png copying images... [ 60%] _static/img/pl-truncate2.png copying images... [ 70%] _static/img/pl-truncate3.png copying images... [ 80%] _static/img/icons/tick.png copying images... [ 90%] _static/img/icons/cross.png copying images... [100%] _static/img/icons/error.png dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 3 warnings. The HTML pages are in _build/html. Build finished. The HTML pages are in _build/html. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py312-powerline-status-2.8.4_1 depends on package: py312-psutil>=3.2.0 - not found ===> Installing existing package /packages/All/py312-psutil-7.2.2_1.pkg [s15amd64-setuptools2-job-04] Installing py312-psutil-7.2.2_1... [s15amd64-setuptools2-job-04] Extracting py312-psutil-7.2.2_1: .......... done ===> py312-powerline-status-2.8.4_1 depends on package: py312-psutil>=3.2.0 - found ===> Returning to build of py312-powerline-status-2.8.4_1 ===> py312-powerline-status-2.8.4_1 depends on file: /usr/local/bin/python3.12 - found =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Staging for py312-powerline-status-2.8.4_1 ===> Generating temporary packing list /usr/local/lib/python3.12/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/local/lib/python3.12/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running install /usr/local/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing powerline_status.egg-info/PKG-INFO writing dependency_links to powerline_status.egg-info/dependency_links.txt writing requirements to powerline_status.egg-info/requires.txt writing top-level names to powerline_status.egg-info/top_level.txt reading manifest file 'powerline_status.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.pyo' found under directory 'powerline/bindings' adding license file 'LICENSE' writing manifest file 'powerline_status.egg-info/SOURCES.txt' /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.awesome' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.awesome' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.awesome' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.awesome' to be distributed and are already explicitly excluding 'powerline.bindings.awesome' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.bar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.bar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.bar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.bar' to be distributed and are already explicitly excluding 'powerline.bindings.bar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.bash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.bash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.bash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.bash' to be distributed and are already explicitly excluding 'powerline.bindings.bash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.fish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.fish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.fish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.fish' to be distributed and are already explicitly excluding 'powerline.bindings.fish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.i3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.i3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.i3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.i3' to be distributed and are already explicitly excluding 'powerline.bindings.i3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.lemonbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.lemonbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.lemonbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.lemonbar' to be distributed and are already explicitly excluding 'powerline.bindings.lemonbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.rc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.rc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.rc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.rc' to be distributed and are already explicitly excluding 'powerline.bindings.rc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.shell' to be distributed and are already explicitly excluding 'powerline.bindings.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.tcsh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.tcsh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.tcsh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.tcsh' to be distributed and are already explicitly excluding 'powerline.bindings.tcsh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.vim.autoload.powerline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.vim.autoload.powerline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.bindings.vim.autoload.powerline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.bindings.vim.autoload.powerline' to be distributed and are already explicitly excluding 'powerline.bindings.vim.autoload.powerline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.bindings.vim.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.bindings.vim.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 'powerline.bindings.vim.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 'powerline.bindings.vim.plugin' to be distributed and are already explicitly excluding 'powerline.bindings.vim.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/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files' to be distributed and are already explicitly excluding 'powerline.config_files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.ipython' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.ipython' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.ipython' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.ipython' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.ipython' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.pdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.pdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.pdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.pdb' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.pdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.shell' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.tmux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.tmux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.tmux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.tmux' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.tmux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.colorschemes.vim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.colorschemes.vim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.colorschemes.vim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.colorschemes.vim' to be distributed and are already explicitly excluding 'powerline.config_files.colorschemes.vim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes' to be distributed and are already explicitly excluding 'powerline.config_files.themes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.ipython' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.ipython' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.ipython' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.ipython' to be distributed and are already explicitly excluding 'powerline.config_files.themes.ipython' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.pdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.pdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.pdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.pdb' to be distributed and are already explicitly excluding 'powerline.config_files.themes.pdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.shell' to be distributed and are already explicitly excluding 'powerline.config_files.themes.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.tmux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.tmux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.tmux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.tmux' to be distributed and are already explicitly excluding 'powerline.config_files.themes.tmux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.vim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.vim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.vim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.vim' to be distributed and are already explicitly excluding 'powerline.config_files.themes.vim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.config_files.themes.wm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.config_files.themes.wm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'powerline.config_files.themes.wm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'powerline.config_files.themes.wm' to be distributed and are already explicitly excluding 'powerline.config_files.themes.wm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'powerline.dist.systemd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'powerline.dist.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 'powerline.dist.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 'powerline.dist.systemd' to be distributed and are already explicitly excluding 'powerline.dist.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) copying powerline/bindings/awesome/powerline-awesome.py -> build/lib/powerline/bindings/awesome copying powerline/bindings/bar/powerline-bar.py -> build/lib/powerline/bindings/bar copying powerline/bindings/i3/powerline-i3.py -> build/lib/powerline/bindings/i3 copying powerline/bindings/lemonbar/powerline-lemonbar.py -> build/lib/powerline/bindings/lemonbar running build_scripts running install_lib creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/dist creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/dist/systemd copying build/lib/powerline/dist/systemd/powerline-daemon.service -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/dist/systemd copying build/lib/powerline/ipython.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers copying build/lib/powerline/renderers/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers copying build/lib/powerline/renderers/i3bar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/bash.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/readline.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/ksh.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/zsh.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/tcsh.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/shell/rcsh.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell copying build/lib/powerline/renderers/vim.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers copying build/lib/powerline/renderers/pdb.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython copying build/lib/powerline/renderers/ipython/since_7.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython copying build/lib/powerline/renderers/ipython/pre_5.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython copying build/lib/powerline/renderers/ipython/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython copying build/lib/powerline/renderers/ipython/since_5.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython copying build/lib/powerline/renderers/tmux.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers copying build/lib/powerline/renderers/lemonbar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers copying build/lib/powerline/renderers/pango_markup.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files copying build/lib/powerline/config_files/config.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes copying build/lib/powerline/config_files/colorschemes/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/tmux copying build/lib/powerline/config_files/colorschemes/tmux/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/tmux copying build/lib/powerline/config_files/colorschemes/tmux/solarized.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/tmux creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/shell copying build/lib/powerline/config_files/colorschemes/shell/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/shell copying build/lib/powerline/config_files/colorschemes/shell/__main__.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/shell copying build/lib/powerline/config_files/colorschemes/shell/solarized.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/shell creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/ipython copying build/lib/powerline/config_files/colorschemes/ipython/__main__.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/ipython creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/pdb copying build/lib/powerline/config_files/colorschemes/pdb/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/pdb copying build/lib/powerline/config_files/colorschemes/pdb/__main__.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/pdb copying build/lib/powerline/config_files/colorschemes/pdb/solarized.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/pdb creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/vim copying build/lib/powerline/config_files/colorschemes/vim/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/vim copying build/lib/powerline/config_files/colorschemes/vim/__main__.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/vim copying build/lib/powerline/config_files/colorschemes/vim/solarizedlight.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/vim copying build/lib/powerline/config_files/colorschemes/vim/solarized.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes/vim copying build/lib/powerline/config_files/colorschemes/solarized.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/colorschemes copying build/lib/powerline/config_files/colors.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/tmux copying build/lib/powerline/config_files/themes/tmux/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/tmux creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/shell copying build/lib/powerline/config_files/themes/shell/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/shell copying build/lib/powerline/config_files/themes/shell/select.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/shell copying build/lib/powerline/config_files/themes/shell/__main__.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/shell copying build/lib/powerline/config_files/themes/shell/continuation.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/shell copying build/lib/powerline/config_files/themes/shell/default_leftonly.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/shell creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/wm copying build/lib/powerline/config_files/themes/wm/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/wm copying build/lib/powerline/config_files/themes/unicode_terminus.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/ipython copying build/lib/powerline/config_files/themes/ipython/in.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/ipython copying build/lib/powerline/config_files/themes/ipython/out.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/ipython copying build/lib/powerline/config_files/themes/ipython/rewrite.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/ipython copying build/lib/powerline/config_files/themes/ipython/in2.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/ipython copying build/lib/powerline/config_files/themes/ascii.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/pdb copying build/lib/powerline/config_files/themes/pdb/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/pdb copying build/lib/powerline/config_files/themes/powerline_unicode7.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes copying build/lib/powerline/config_files/themes/powerline.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes copying build/lib/powerline/config_files/themes/unicode.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes copying build/lib/powerline/config_files/themes/unicode_terminus_condensed.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/default.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/plugin_nerdtree.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/plugin_commandt.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/cmdwin.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/help.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/__main__.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/plugin_gundo.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/quickfix.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/tabline.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/vim/plugin_gundo-preview.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes/vim copying build/lib/powerline/config_files/themes/powerline_terminus.json -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config_files/themes creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers copying build/lib/powerline/matchers/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim copying build/lib/powerline/matchers/vim/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin copying build/lib/powerline/matchers/vim/plugin/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin copying build/lib/powerline/matchers/vim/plugin/nerdtree.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin copying build/lib/powerline/matchers/vim/plugin/gundo.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin copying build/lib/powerline/matchers/vim/plugin/commandt.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/lint/context.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/lint/checks.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/lint/imp.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/lint/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/lint/spec.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/lint/inspect.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/nodes.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/loader.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/reader.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/events.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/tokens.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/composer.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/markedvalue.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/resolver.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/scanner.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/parser.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/error.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/markedjson/constructor.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson copying build/lib/powerline/lint/selfcheck.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint copying build/lib/powerline/segment.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/memoize.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/encoding.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/inotify.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/shell.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/debug.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/dict.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/overrides.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/path.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher copying build/lib/powerline/lib/watcher/tree.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher copying build/lib/powerline/lib/watcher/inotify.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher copying build/lib/powerline/lib/watcher/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher copying build/lib/powerline/lib/watcher/stat.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher copying build/lib/powerline/lib/watcher/uv.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher copying build/lib/powerline/lib/threaded.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/config.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/monotonic.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/url.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/lib/humanize_bytes.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs copying build/lib/powerline/lib/vcs/bzr.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs copying build/lib/powerline/lib/vcs/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs copying build/lib/powerline/lib/vcs/git.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs copying build/lib/powerline/lib/vcs/mercurial.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs copying build/lib/powerline/lib/unicode.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib copying build/lib/powerline/shell.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline copying build/lib/powerline/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline copying build/lib/powerline/version.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/net.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/mail.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/bat.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/players.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/sys.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/time.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/wthr.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/env.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/common/vcs.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common copying build/lib/powerline/segments/ipython.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments copying build/lib/powerline/segments/shell.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments copying build/lib/powerline/segments/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments copying build/lib/powerline/segments/pdb.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments copying build/lib/powerline/segments/i3wm.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments copying build/lib/powerline/segments/tmux.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim copying build/lib/powerline/segments/vim/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/syntastic.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/ale.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/coc.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/nerdtree.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/commandt.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/capslock.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/segments/vim/plugin/tagbar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin copying build/lib/powerline/colorscheme.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers copying build/lib/powerline/listers/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers copying build/lib/powerline/listers/vim.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers copying build/lib/powerline/listers/pdb.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers copying build/lib/powerline/listers/i3wm.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers copying build/lib/powerline/vim.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline copying build/lib/powerline/pdb.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/commands/main.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/commands/daemon.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/commands/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/commands/config.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/commands/lint.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/commands/lemonbar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands copying build/lib/powerline/renderer.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/selectors copying build/lib/powerline/selectors/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/selectors copying build/lib/powerline/selectors/vim.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/selectors copying build/lib/powerline/config.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline copying build/lib/powerline/theme.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/awesome copying build/lib/powerline/bindings/awesome/powerline-awesome.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/awesome copying build/lib/powerline/bindings/awesome/powerline.lua -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/awesome creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/bar copying build/lib/powerline/bindings/bar/powerline-bar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/bar creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/fish copying build/lib/powerline/bindings/fish/powerline-setup.fish -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/fish creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/zsh copying build/lib/powerline/bindings/zsh/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/zsh copying build/lib/powerline/bindings/zsh/powerline.zsh -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/zsh creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline_tmux_1.8.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline-base.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline_tmux_1.7_plus.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline_tmux_1.8_minus.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline_tmux_2.1_plus.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline_tmux_1.8_plus.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux copying build/lib/powerline/bindings/tmux/powerline_tmux_1.9_plus.conf -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/bash copying build/lib/powerline/bindings/bash/powerline.sh -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/bash copying build/lib/powerline/bindings/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/lemonbar copying build/lib/powerline/bindings/lemonbar/powerline-lemonbar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/lemonbar creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/qtile copying build/lib/powerline/bindings/qtile/widget.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/qtile copying build/lib/powerline/bindings/qtile/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/qtile creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/shell copying build/lib/powerline/bindings/shell/powerline.sh -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/shell creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/wm copying build/lib/powerline/bindings/wm/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/wm copying build/lib/powerline/bindings/wm/awesome.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/wm creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/rc copying build/lib/powerline/bindings/rc/powerline.rc -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/rc creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython copying build/lib/powerline/bindings/ipython/since_7.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython copying build/lib/powerline/bindings/ipython/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython copying build/lib/powerline/bindings/ipython/post_0_11.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython copying build/lib/powerline/bindings/ipython/pre_0_11.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython copying build/lib/powerline/bindings/ipython/since_5.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/i3 copying build/lib/powerline/bindings/i3/powerline-i3.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/i3 creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/pdb copying build/lib/powerline/bindings/pdb/__main__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/pdb copying build/lib/powerline/bindings/pdb/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/pdb copying build/lib/powerline/bindings/config.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim copying build/lib/powerline/bindings/vim/__init__.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim/plugin copying build/lib/powerline/bindings/vim/plugin/powerline.vim -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim/plugin creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim/autoload creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim/autoload/powerline copying build/lib/powerline/bindings/vim/autoload/powerline/debug.vim -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim/autoload/powerline creating /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tcsh copying build/lib/powerline/bindings/tcsh/powerline.tcsh -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tcsh copying build/lib/powerline/lemonbar.py -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/ipython.py to ipython.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/i3bar.py to i3bar.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/bash.py to bash.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/readline.py to readline.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/ksh.py to ksh.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/zsh.py to zsh.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/tcsh.py to tcsh.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/shell/rcsh.py to rcsh.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/vim.py to vim.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/pdb.py to pdb.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython/since_7.py to since_7.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython/pre_5.py to pre_5.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/ipython/since_5.py to since_5.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/tmux.py to tmux.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/lemonbar.py to lemonbar.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderers/pango_markup.py to pango_markup.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin/nerdtree.py to nerdtree.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin/gundo.py to gundo.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/matchers/vim/plugin/commandt.py to commandt.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/context.py to context.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/checks.py to checks.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/imp.py to imp.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/spec.py to spec.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/inspect.py to inspect.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/nodes.py to nodes.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/loader.py to loader.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/reader.py to reader.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/events.py to events.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/tokens.py to tokens.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/composer.py to composer.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/markedvalue.py to markedvalue.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/resolver.py to resolver.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/scanner.py to scanner.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/parser.py to parser.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/error.py to error.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/markedjson/constructor.py to constructor.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lint/selfcheck.py to selfcheck.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segment.py to segment.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/memoize.py to memoize.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/encoding.py to encoding.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/inotify.py to inotify.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/shell.py to shell.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/debug.py to debug.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/dict.py to dict.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/overrides.py to overrides.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/path.py to path.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher/tree.py to tree.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher/inotify.py to inotify.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher/stat.py to stat.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/watcher/uv.py to uv.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/threaded.py to threaded.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/config.py to config.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/monotonic.py to monotonic.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/url.py to url.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/humanize_bytes.py to humanize_bytes.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs/bzr.py to bzr.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs/git.py to git.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/vcs/mercurial.py to mercurial.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lib/unicode.py to unicode.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/shell.py to shell.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/version.py to version.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/net.py to net.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/mail.py to mail.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/bat.py to bat.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/players.py to players.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/sys.py to sys.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/time.py to time.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/wthr.py to wthr.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/env.py to env.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/common/vcs.py to vcs.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/ipython.py to ipython.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/shell.py to shell.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/pdb.py to pdb.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/i3wm.py to i3wm.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/tmux.py to tmux.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/syntastic.py to syntastic.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/ale.py to ale.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/coc.py to coc.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/nerdtree.py to nerdtree.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/commandt.py to commandt.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/capslock.py to capslock.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/segments/vim/plugin/tagbar.py to tagbar.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/colorscheme.py to colorscheme.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers/vim.py to vim.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers/pdb.py to pdb.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/listers/i3wm.py to i3wm.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/vim.py to vim.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/pdb.py to pdb.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands/main.py to main.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands/daemon.py to daemon.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands/config.py to config.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands/lint.py to lint.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/commands/lemonbar.py to lemonbar.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/renderer.py to renderer.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/selectors/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/selectors/vim.py to vim.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/config.py to config.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/theme.py to theme.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/awesome/powerline-awesome.py to powerline-awesome.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/bar/powerline-bar.py to powerline-bar.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/zsh/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/tmux/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/lemonbar/powerline-lemonbar.py to powerline-lemonbar.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/qtile/widget.py to widget.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/qtile/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/wm/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/wm/awesome.py to awesome.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython/since_7.py to since_7.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython/post_0_11.py to post_0_11.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython/pre_0_11.py to pre_0_11.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/ipython/since_5.py to since_5.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/i3/powerline-i3.py to powerline-i3.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/pdb/__main__.py to __main__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/pdb/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/config.py to config.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/bindings/vim/__init__.py to __init__.cpython-312.pyc byte-compiling /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline/lemonbar.py to lemonbar.cpython-312.pyc writing byte-compilation script '/tmp/tmpsc_fjznz.py' /usr/local/bin/python3.12 /tmp/tmpsc_fjznz.py removing /tmp/tmpsc_fjznz.py running install_data copying scripts/powerline -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin running install_egg_info Copying powerline_status.egg-info to /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/lib/python3.12/site-packages/powerline_status-2.8.4-py3.12.egg-info running install_scripts copying build/scripts-3.12/powerline-config -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin copying build/scripts-3.12/powerline-daemon -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin copying build/scripts-3.12/powerline-lint -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin copying build/scripts-3.12/powerline-render -> /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin changing mode of /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin/powerline-config to 755 changing mode of /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin/powerline-daemon to 755 changing mode of /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin/powerline-lint to 755 changing mode of /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin/powerline-render to 755 writing list of installed files to '/wrkdirs/usr/ports/misc/py-powerline-status/work-py312/.PLIST.pymodtmp' install -m 0644 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/man/powerline.1 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/share/man/man1 install -m 0644 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/man/powerline-daemon.1 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/share/man/man1 install -m 0644 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/man/powerline-lint.1 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/share/man/man1 install -m 0644 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/man/powerline-config.1 /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/share/man/man1 cd /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/powerline-2.8.4/docs/_build/html && /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) && /usr/bin/find -Ed $1 $3 \( -type d -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 755 "$@"'\'' . {} + -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE . /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/share/doc/powerline-status '! -name .buildinfo' /usr/bin/strip /wrkdirs/usr/ports/misc/py-powerline-status/work-py312/stage/usr/local/bin/powerline ====> Compressing man pages (compress-man) =========================================================================== =================================================== ===== env: 'PKG_NOTES=build_timestamp ports_top_git_hash ports_top_checkout_unclean port_git_hash port_checkout_unclean built_by' 'PKG_NOTE_build_timestamp=2026-07-08T00:21:57+0000' 'PKG_NOTE_ports_top_git_hash=18628b9022c9c1c0e7cb5e71c2aa1e1e563ca34a' 'PKG_NOTE_ports_top_checkout_unclean=yes' 'PKG_NOTE_port_git_hash=1c3394560c4f3b7e3e79480f17b767e3a58bd951' 'PKG_NOTE_port_checkout_unclean=no' 'PKG_NOTE_built_by=poudriere-git-3.4.8' NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Building packages for py312-powerline-status-2.8.4_1 ===> Building py312-powerline-status-2.8.4_1 =========================================================================== =>> Cleaning up wrkdir ===> Cleaning for py312-powerline-status-2.8.4_1 build of misc/py-powerline-status@py312 | py312-powerline-status-2.8.4_1 ended at Wed Jul 8 09:23:55 JST 2026 build time: 00:02:09