Package: src:powerline
Version: 2.8.3-6
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary
dh binary --with sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning:
Unknown distribution option: 'test_suite'
warnings.warn(msg)
running build
[... snipped ...]
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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/lib/python3/dist-packages/setuptools/command/build_py.py:218: _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
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files
copying powerline/config_files/colors.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files
copying powerline/config_files/config.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes
copying powerline/config_files/colorschemes/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes
copying powerline/config_files/colorschemes/solarized.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/ipython
copying powerline/config_files/colorschemes/ipython/__main__.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/ipython
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/pdb
copying powerline/config_files/colorschemes/pdb/__main__.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/pdb
copying powerline/config_files/colorschemes/pdb/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/pdb
copying powerline/config_files/colorschemes/pdb/solarized.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/pdb
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/shell
copying powerline/config_files/colorschemes/shell/__main__.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/shell
copying powerline/config_files/colorschemes/shell/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/shell
copying powerline/config_files/colorschemes/shell/solarized.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/shell
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/tmux
copying powerline/config_files/colorschemes/tmux/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/tmux
copying powerline/config_files/colorschemes/tmux/solarized.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/tmux
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/vim
copying powerline/config_files/colorschemes/vim/__main__.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/vim
copying powerline/config_files/colorschemes/vim/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/vim
copying powerline/config_files/colorschemes/vim/solarized.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/vim
copying powerline/config_files/colorschemes/vim/solarizedlight.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/colorschemes/vim
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/ascii.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/powerline.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/powerline_terminus.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/powerline_unicode7.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/unicode.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/unicode_terminus.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
copying powerline/config_files/themes/unicode_terminus_condensed.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/ipython
copying powerline/config_files/themes/ipython/in.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/ipython
copying powerline/config_files/themes/ipython/in2.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/ipython
copying powerline/config_files/themes/ipython/out.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/ipython
copying powerline/config_files/themes/ipython/rewrite.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/ipython
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/pdb
copying powerline/config_files/themes/pdb/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/pdb
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/shell
copying powerline/config_files/themes/shell/__main__.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/shell
copying powerline/config_files/themes/shell/continuation.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/shell
copying powerline/config_files/themes/shell/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/shell
copying powerline/config_files/themes/shell/default_leftonly.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/shell
copying powerline/config_files/themes/shell/select.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/shell
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/tmux
copying powerline/config_files/themes/tmux/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/tmux
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/__main__.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/cmdwin.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/help.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/plugin_commandt.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/plugin_gundo-preview.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/plugin_gundo.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/plugin_nerdtree.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/quickfix.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
copying powerline/config_files/themes/vim/tabline.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/vim
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/wm
copying powerline/config_files/themes/wm/default.json ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/config_files/themes/wm
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/dist
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/dist/systemd
copying powerline/dist/systemd/powerline-daemon.service ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/dist/systemd
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/awesome
copying powerline/bindings/awesome/powerline-awesome.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/awesome
copying powerline/bindings/awesome/powerline.lua ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/awesome
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/bar
copying powerline/bindings/bar/powerline-bar.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/bar
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/bash
copying powerline/bindings/bash/powerline.sh ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/bash
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/fish
copying powerline/bindings/fish/powerline-setup.fish ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/fish
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/i3
copying powerline/bindings/i3/powerline-i3.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/i3
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/lemonbar
copying powerline/bindings/lemonbar/powerline-lemonbar.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/lemonbar
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/rc
copying powerline/bindings/rc/powerline.rc ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/rc
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/shell
copying powerline/bindings/shell/powerline.sh ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/shell
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tcsh
copying powerline/bindings/tcsh/powerline.tcsh ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tcsh
copying powerline/bindings/tmux/powerline-base.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline_tmux_1.7_plus.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline_tmux_1.8.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline_tmux_1.8_minus.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline_tmux_1.8_plus.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline_tmux_1.9_plus.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
copying powerline/bindings/tmux/powerline_tmux_2.1_plus.conf ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/tmux
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/vim/autoload
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/vim/autoload/powerline
copying powerline/bindings/vim/autoload/powerline/debug.vim ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/vim/autoload/powerline
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/vim/plugin
copying powerline/bindings/vim/plugin/powerline.vim ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/vim/plugin
copying powerline/bindings/zsh/powerline.zsh ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/zsh
running build_scripts
creating build
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
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build; python3.12 -m unittest
discover -v
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/lint/__init__.py:44:
SyntaxWarning: invalid escape sequence '\w'
function_name_re = '^(\w+\.)*[a-zA-Z_]\w*$'
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/lint/__init__.py:208:
SyntaxWarning: invalid escape sequence '\w'
shell_mode_spec = Spec().re('^(?:[\w\-]+|\.safe)$').copy
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/lint/__init__.py:226:
SyntaxWarning: invalid escape sequence '\w'
name=Spec().re('^[a-zA-Z_]\w*$').optional(),
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/lint/spec.py:24:
SyntaxWarning: invalid escape sequence '\w'
'''Class that describes some JSON value
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/lint/spec.py:588:
SyntaxWarning: invalid escape sequence '\w'
return self.re('^\w+(?::\w+)?$', msg_func)
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/tests/modules/lib/__init__.py:51:
SyntaxWarning: invalid escape sequence '\/'
return '{"city":"Meppen","country":{"name":"Germany",
"code":"DE"},"location":{"accuracy_radius":100,"latitude":52.6833,"longitude":7.3167,"time_zone":"Europe\/Berlin"},"ip":"82.145.55.16"}'
powerline.bindings.zsh (unittest.loader._FailedTest.powerline.bindings.zsh) ...
ERROR
======================================================================
ERROR: powerline.bindings.zsh
(unittest.loader._FailedTest.powerline.bindings.zsh)
----------------------------------------------------------------------
ImportError: Failed to import test module: powerline.bindings.zsh
Traceback (most recent call last):
File "/usr/lib/python3.12/unittest/loader.py", line 429, in _find_test_path
package = self._get_module_from_name(name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/unittest/loader.py", line 339, in
_get_module_from_name
__import__(name)
File
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build/powerline/bindings/zsh/__init__.py",
line 8, in <module>
import zsh
ModuleNotFoundError: No module named 'zsh'
----------------------------------------------------------------------
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_powerline/build; python3.12 -m unittest
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit
code 13
make: *** [debian/rules:10: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202408/
About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
