--- Begin Message ---
Source: python-flasgger
Version: 0.9.5+dfsg.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
> dh_update_autotools_config -O--buildsystem=pybuild
> dh_autoreconf -O--buildsystem=pybuild
> dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config
> running config
> I: pybuild base:310: python3.11 setup.py config
> running config
> dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> copying flasgger/utils.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> copying flasgger/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> copying flasgger/marshmallow_apispec.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> copying flasgger/base.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> copying flasgger/constants.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> running egg_info
> creating flasgger.egg-info
> writing flasgger.egg-info/PKG-INFO
> writing dependency_links to flasgger.egg-info/dependency_links.txt
> writing requirements to flasgger.egg-info/requires.txt
> writing top-level names to flasgger.egg-info/top_level.txt
> writing manifest file 'flasgger.egg-info/SOURCES.txt'
> reading manifest file 'flasgger.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*' under directory 'flasgger/ui2'
> warning: no files found matching '*' under directory 'flasgger/ui2/static'
> warning: no files found matching '*' under directory 'flasgger/ui2/static/css'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/static/fonts'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/static/images'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/static/lang'
> warning: no files found matching '*' under directory 'flasgger/ui2/static/lib'
> warning: no files found matching '*' under directory 'flasgger/ui2/templates'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/templates/flasgger'
> warning: no files found matching '*' under directory 'flasgger/ui3/static/css'
> warning: no files found matching '*' under directory
> 'flasgger/ui3/static/fonts'
> warning: no files found matching '*' under directory
> 'flasgger/ui3/static/images'
> warning: no files found matching '*' under directory
> 'flasgger/ui3/static/lang'
> warning: no previously-included files matching '__pycache__' found under
> directory 'flasgger'
> warning: no previously-included files matching '*.py[co]' found under
> directory 'flasgger'
> adding license file 'LICENSE'
> writing manifest file 'flasgger.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3' to be distributed and are
> already explicitly excluding 'flasgger.ui3' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.static' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.static' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.static' is explicitly
> added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.static' to be distributed and are
> already explicitly excluding 'flasgger.ui3.static' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.static.lib' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.static.lib' as an importable
> package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.static.lib' is
> explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.static.lib' to be distributed and are
> already explicitly excluding 'flasgger.ui3.static.lib' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.templates' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.templates' as an importable
> package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.templates' is explicitly
> added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.templates' to be distributed and are
> already explicitly excluding 'flasgger.ui3.templates' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.templates.flasgger' is absent from the `packages`
> configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.templates.flasgger' as an importable
> package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.templates.flasgger' is
> explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.templates.flasgger' to be distributed
> and are
> already explicitly excluding 'flasgger.ui3.templates.flasgger' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.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 flasgger/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3
> copying flasgger/ui3/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/favicon-16x16.png ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/favicon-32x32.png ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-bundle.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-bundle.js.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-standalone-preset.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-standalone-preset.js.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.css ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.css.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.js.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static/lib
> copying flasgger/ui3/static/lib/jquery.min.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static/lib
> copying flasgger/ui3/static/lib/jquery.min.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/static/lib
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates
> copying flasgger/ui3/templates/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/body_scripts.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/custom_head.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/footer.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/head.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/index.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/oauth2-redirect.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/swagger.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/top.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/ui3/templates/flasgger
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> copying flasgger/utils.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> copying flasgger/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> copying flasgger/marshmallow_apispec.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> copying flasgger/base.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> copying flasgger/constants.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> running egg_info
> writing flasgger.egg-info/PKG-INFO
> writing dependency_links to flasgger.egg-info/dependency_links.txt
> writing requirements to flasgger.egg-info/requires.txt
> writing top-level names to flasgger.egg-info/top_level.txt
> reading manifest file 'flasgger.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*' under directory 'flasgger/ui2'
> warning: no files found matching '*' under directory 'flasgger/ui2/static'
> warning: no files found matching '*' under directory 'flasgger/ui2/static/css'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/static/fonts'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/static/images'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/static/lang'
> warning: no files found matching '*' under directory 'flasgger/ui2/static/lib'
> warning: no files found matching '*' under directory 'flasgger/ui2/templates'
> warning: no files found matching '*' under directory
> 'flasgger/ui2/templates/flasgger'
> warning: no files found matching '*' under directory 'flasgger/ui3/static/css'
> warning: no files found matching '*' under directory
> 'flasgger/ui3/static/fonts'
> warning: no files found matching '*' under directory
> 'flasgger/ui3/static/images'
> warning: no files found matching '*' under directory
> 'flasgger/ui3/static/lang'
> warning: no previously-included files matching '__pycache__' found under
> directory 'flasgger'
> warning: no previously-included files matching '*.py[co]' found under
> directory 'flasgger'
> adding license file 'LICENSE'
> writing manifest file 'flasgger.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3' is explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3' to be distributed and are
> already explicitly excluding 'flasgger.ui3' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.static' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.static' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.static' is explicitly
> added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.static' to be distributed and are
> already explicitly excluding 'flasgger.ui3.static' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.static.lib' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.static.lib' as an importable
> package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.static.lib' is
> explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.static.lib' to be distributed and are
> already explicitly excluding 'flasgger.ui3.static.lib' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.templates' is absent from the `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.templates' as an importable
> package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.templates' is explicitly
> added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.templates' to be distributed and are
> already explicitly excluding 'flasgger.ui3.templates' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.py` files.
> On the other hand, currently there is no concept of package data
> directory, all directories are treated like packages.
>
> ********************************************************************************
>
> !!
> check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning:
> Package 'flasgger.ui3.templates.flasgger' is absent from the `packages`
> configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'flasgger.ui3.templates.flasgger' as an importable
> package[^1],
> but it is absent from setuptools' `packages` configuration.
>
> This leads to an ambiguous overall configuration. If you want to
> distribute this
> package, please make sure that 'flasgger.ui3.templates.flasgger' is
> explicitly added
> to the `packages` configuration field.
>
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" on setuptools
> documentation page:
>
> -
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
>
> If you don't want 'flasgger.ui3.templates.flasgger' to be distributed
> and are
> already explicitly excluding 'flasgger.ui3.templates.flasgger' via
> `find_namespace_packages(...)/find_namespace` or
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
>
> You can read more about "package data files" on setuptools
> documentation page:
>
> - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
>
>
> [^1]: For Python, any directory (with suitable naming) can be
> imported,
> even if it does not contain any `.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 flasgger/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3
> copying flasgger/ui3/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/favicon-16x16.png ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/favicon-32x32.png ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-bundle.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-bundle.js.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-standalone-preset.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui-standalone-preset.js.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.css ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.css.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> copying flasgger/ui3/static/swagger-ui.js.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static/lib
> copying flasgger/ui3/static/lib/jquery.min.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static/lib
> copying flasgger/ui3/static/lib/jquery.min.map ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/static/lib
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates
> copying flasgger/ui3/templates/.DS_Store ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/body_scripts.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/custom_head.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/footer.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/head.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/index.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/oauth2-redirect.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/swagger.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> copying flasgger/ui3/templates/flasgger/top.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build/flasgger/ui3/templates/flasgger
> dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build; python3.12 -m
> unittest discover -v
> flasgger (unittest.loader._FailedTest.flasgger) ... ERROR
>
> ======================================================================
> ERROR: flasgger (unittest.loader._FailedTest.flasgger)
> ----------------------------------------------------------------------
> ImportError: Failed to import test module: flasgger
> Traceback (most recent call last):
> File "/usr/lib/python3.12/unittest/loader.py", line 427, in _find_test_path
> package = self._get_module_from_name(name)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/unittest/loader.py", line 337, in
> _get_module_from_name
> __import__(name)
> File
> "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/__init__.py",
> line 10, in <module>
> from .base import Swagger, Flasgger, NO_SANITIZER, BR_SANITIZER,
> MK_SANITIZER, LazyJSONEncoder # noqa
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File
> "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/base.py",
> line 36, in <module>
> from .utils import extract_definitions
> File
> "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger/utils.py",
> line 5, in <module>
> import imp
> ModuleNotFoundError: No module named 'imp'
>
>
> ----------------------------------------------------------------------
> Ran 1 test in 0.000s
>
> FAILED (errors=1)
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build; python3.12 -m
> unittest discover -v
> I: pybuild base:310: cd
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_flasgger/build; python3.11 -m
> unittest discover -v
>
> ----------------------------------------------------------------------
> Ran 0 tests in 0.000s
>
> OK
> dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11"
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-flasgger_0.9.5+dfsg.2-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&[email protected]&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
