Your message dated Tue, 04 Mar 2025 10:36:05 +0000
with message-id <[email protected]>
and subject line Bug#1098599: fixed in python-flasgger 0.9.7.2~dev2+dfsg-4
has caused the Debian Bug report #1098599,
regarding python-flasgger: FTBFS: E       TypeError: CliRunner.__init__() got 
an unexpected keyword argument 'mix_stderr'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1098599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098599
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:python-flasgger
Version: 0.9.7.2~dev2+dfsg-3
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py clean 
running clean
removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build' (and 
everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.12' does not exist -- can't clean it
I: pybuild base:311: python3.13 setup.py clean 
running clean
removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build' (and 
everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.13' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 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:311: python3.12 setup.py config 
running config
I: pybuild base:311: python3.13 setup.py config 
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build 
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/constants.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/commands.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/marshmallow_apispec.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/utils.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/compatible.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/__init__.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build/flasgger
copying flasgger/base.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 entry points to flasgger.egg-info/entry_points.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:212: _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:212: _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:212: _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/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/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:311: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/constants.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/commands.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/marshmallow_apispec.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/utils.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/compatible.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/__init__.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
copying flasgger/base.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger
running egg_info
writing flasgger.egg-info/PKG-INFO
writing dependency_links to flasgger.egg-info/dependency_links.txt
writing entry points to flasgger.egg-info/entry_points.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:212: _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:212: _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:212: _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.13_flasgger/build/flasgger
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/favicon-16x16.png -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/favicon-32x32.png -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui-bundle.js -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui-bundle.js.map -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui-standalone-preset.js -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui-standalone-preset.js.map -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui.css -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui.css.map -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui.js -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
copying flasgger/ui3/static/swagger-ui.js.map -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static/lib
copying flasgger/ui3/static/lib/jquery.min.js -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static/lib
copying flasgger/ui3/static/lib/jquery.min.map -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/static/lib
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/body_scripts.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/custom_head.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/footer.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/head.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/index.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/oauth2-redirect.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/swagger.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
copying flasgger/ui3/templates/flasgger/top.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build/flasgger/ui3/templates/flasgger
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd 
'/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build'; python3.12 -m pytest 
--ignore tests/test_examples.py
============================= test session starts ==============================
platform linux -- Python 3.12.9, pytest-8.3.4, pluggy-1.5.0
rootdir: /<<PKGBUILDDIR>>
plugins: typeguard-4.4.1
collected 10 items

tests/test_apispecs.py .                                                 [ 10%]
tests/test_base.py ...                                                   [ 40%]
tests/test_commands.py EEEE                                              [ 80%]
tests/test_utils.py ..                                                   [100%]

==================================== ERRORS ====================================
_____________________ ERROR at setup of test_default_specs _____________________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f0a29f38f80>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
_____________________ ERROR at setup of test_custom_specs ______________________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f0a29f37e30>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
___________________ ERROR at setup of test_invalid_endpoint ____________________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f0a29f39100>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
_________ ERROR at setup of test_definitions_is_removed_for_openapi_3 __________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f0a29f3b890>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
=========================== short test summary info ============================
ERROR tests/test_commands.py::test_default_specs - TypeError: CliRunner.__ini...
ERROR tests/test_commands.py::test_custom_specs - TypeError: CliRunner.__init...
ERROR tests/test_commands.py::test_invalid_endpoint - TypeError: CliRunner.__...
ERROR tests/test_commands.py::test_definitions_is_removed_for_openapi_3 - Typ...
========================= 6 passed, 4 errors in 0.10s ==========================
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
'/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_flasgger/build'; python3.12 -m pytest 
--ignore tests/test_examples.py
I: pybuild base:311: cd 
'/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build'; python3.13 -m pytest 
--ignore tests/test_examples.py
============================= test session starts ==============================
platform linux -- Python 3.13.2, pytest-8.3.4, pluggy-1.5.0
rootdir: /<<PKGBUILDDIR>>
plugins: typeguard-4.4.1
collected 10 items

tests/test_apispecs.py .                                                 [ 10%]
tests/test_base.py ...                                                   [ 40%]
tests/test_commands.py EEEE                                              [ 80%]
tests/test_utils.py ..                                                   [100%]

==================================== ERRORS ====================================
_____________________ ERROR at setup of test_default_specs _____________________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f9cb78fd400>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
_____________________ ERROR at setup of test_custom_specs ______________________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f9cb777c2d0>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
___________________ ERROR at setup of test_invalid_endpoint ____________________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f9cb777d1d0>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
_________ ERROR at setup of test_definitions_is_removed_for_openapi_3 __________

app = <Flask 'conftest'>

    @pytest.fixture(scope="function")
    def cli_runner(app):
>       yield app.test_cli_runner(mix_stderr=False)

tests/conftest.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/flask/app.py:742: in test_cli_runner
    return cls(self, **kwargs)  # type: ignore
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <flask.testing.FlaskCliRunner object at 0x7f9cb7778c30>
app = <Flask 'conftest'>, kwargs = {'mix_stderr': False}

    def __init__(self, app: Flask, **kwargs: t.Any) -> None:
        self.app = app
>       super().__init__(**kwargs)
E       TypeError: CliRunner.__init__() got an unexpected keyword argument 
'mix_stderr'

/usr/lib/python3/dist-packages/flask/testing.py:272: TypeError
=========================== short test summary info ============================
ERROR tests/test_commands.py::test_default_specs - TypeError: CliRunner.__ini...
ERROR tests/test_commands.py::test_custom_specs - TypeError: CliRunner.__init...
ERROR tests/test_commands.py::test_invalid_endpoint - TypeError: CliRunner.__...
ERROR tests/test_commands.py::test_definitions_is_removed_for_openapi_3 - Typ...
========================= 6 passed, 4 errors in 0.08s ==========================
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
'/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_flasgger/build'; python3.13 -m pytest 
--ignore tests/test_examples.py
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
3.13" returned exit code 13
make: *** [debian/rules:6: 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/202502/

About the archive rebuild: The build was made on virtual machines 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 add an affects on src:python-flasgger, so that this is still
visible in the BTS web page for this package.

Thanks.

--- End Message ---
--- Begin Message ---
Source: python-flasgger
Source-Version: 0.9.7.2~dev2+dfsg-4
Done: Colin Watson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
python-flasgger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated python-flasgger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 04 Mar 2025 10:20:03 +0000
Source: python-flasgger
Architecture: source
Version: 0.9.7.2~dev2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1098599
Changes:
 python-flasgger (0.9.7.2~dev2+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix tests with Click 8.2 (closes: #1098599).
Checksums-Sha1:
 078ac7e85137ef58d1ed4cb1fe3508a123346f67 2400 
python-flasgger_0.9.7.2~dev2+dfsg-4.dsc
 d42a3b7112835c3d8e85159ef3389ffad4fceb8e 3078808 
python-flasgger_0.9.7.2~dev2+dfsg-4.debian.tar.xz
Checksums-Sha256:
 c2315fd19c54aca5e5064aaef127c5798447817694330e6b05fdab9dbb1bf043 2400 
python-flasgger_0.9.7.2~dev2+dfsg-4.dsc
 f02c107f79839a5e5b37f89b3796a697d7d6d1c418f7c23711e73ed59a564211 3078808 
python-flasgger_0.9.7.2~dev2+dfsg-4.debian.tar.xz
Files:
 5634c8aeb0ecf4ab77656f9cca2c057e 2400 python optional 
python-flasgger_0.9.7.2~dev2+dfsg-4.dsc
 b593897518030614c6c56998114d8ea9 3078808 python optional 
python-flasgger_0.9.7.2~dev2+dfsg-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmfG1BYACgkQOTWH2X2G
UAtkFhAAgL/YL8ot+2oyjS6McCHz4egUVokZOSbGtt4Uaaw4boRt/pmVsNRBlAeg
at/JbE0+tJ0yPoHaFi5VFCMhdcgr69dVgoElkVNSgesCfAP/vxCcxByrPTo0Nr6F
QIDKONHeYlqykVMaysrW3WrINfAAIhrQf8lnweTBNN0tXxy7qzHgGLxg+UUZQmvI
Lj3E/eL3ja6Y7wVI879IsYelzA/PNCoi7x0iVO4fF5bJ5uR3L8tdPaX3I+MuD5nb
Gk5+L3tfNlCVHwmNerkst7E3sRvUaeYzUHAF+yCPoL5EWjieP2ta4ip6DZGtlhxo
WmCQkvWG/Ijnl4chxdSrqOxKjc+PRvJu5jyoqUc5ak76K70BPocjPmtuWgu2BxHA
e+3Djb8r0sVba26eblnAnrfYO5jf0wHbIqgUJasI+SaKnjaV4ZoFbgytaYYTls14
N+wQN5co5Moo6OAEBQmk58wXPtCOs2dfgD/JNbd6tvXVhzZGovWz6g0Z+qGA4THJ
uRX0QcJZzSgfYIbZYy7SSuDNjQaQHQIwumb0YZj5Ji9ylKWTdYOHOrjqNliWT1va
r3STdxqVlndeOE2itvHGKgfEg7ubn7lsdWES9ZsEUSp+YIl3TNT591IQ9B2snWj+
86cKDViAflXufjHR7hKYCwix7o2jH2+7JtSd3hYstyLz/CZNm4I=
=jIyR
-----END PGP SIGNATURE-----

Attachment: pgp4XbXPFB1_J.pgp
Description: PGP signature


--- End Message ---

Reply via email to