Your message dated Tue, 16 Jun 2026 16:51:05 +0000
with message-id <[email protected]>
and subject line Bug#1139417: fixed in python-webargs 8.7.1-2
has caused the Debian Bug report #1139417,
regarding python-webargs: FTBFS with aiohttp 3.14
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.)


-- 
1139417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139417
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:python-webargs
Version: 8.7.1-1
Severity: serious
Tags: ftbfs forky sid
User: [email protected]
Usertags: aiohttp-3.14

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202606/

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 cannot 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-webargs, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:142: Building wheel for python3.14 with "build" 
module
I: pybuild base:385: python3.14 -m build --skip-dependency-check --no-isolation 
--wheel --outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_webargs  
* Building wheel...
Successfully built webargs-8.7.1-py3-none-any.whl
I: pybuild plugin_pyproject:168: Unpacking wheel built for python3.14 with 
"installer" module
I: pybuild plugin_pyproject:142: Building wheel for python3.13 with "build" 
module
I: pybuild base:385: python3.13 -m build --skip-dependency-check --no-isolation 
--wheel --outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_webargs  
* Building wheel...
Successfully built webargs-8.7.1-py3-none-any.whl
I: pybuild plugin_pyproject:168: Unpacking wheel built for python3.13 with 
"installer" module
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:385: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_webargs/build; 
python3.14 -m pytest -k 'not test_get_path_param and not 
test_get_with_no_json_body and not test_post and not 
test_missing_required_field_throws_422 and not test_required_field_provided and 
not test_use_kwargs_with_error and not 
test_user_validator_returns_422_by_default'
============================= test session starts ==============================
platform linux -- Python 3.14.5, pytest-9.0.3, pluggy-1.6.0
rootdir: /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_webargs/build
configfile: pyproject.toml
plugins: asyncio-1.4.0, typeguard-4.4.4
asyncio: mode=Mode.STRICT, debug=False, 
asyncio_default_fixture_loop_scope=None, 
asyncio_default_test_loop_scope=function
collected 457 items

tests/test_bottleparser.py ........................................s     [  8%]
tests/test_core.py ..................................................... [ 20%]
........................................................................ [ 36%]
..............                                                           [ 39%]
tests/test_djangoparser.py ........................................s.... [ 49%]
.                                                                        [ 49%]
tests/test_falconparser.py .....................................s....... [ 59%]
......                                                                   [ 60%]
tests/test_flaskparser.py .............................................. [ 70%]
..........................................................               [ 83%]
tests/test_pyramidparser.py ...........................................  [ 92%]
tests/test_tornadoparser.py ............F....................            [100%]

=================================== FAILURES ===================================
__________ TestJSONArgs.test_it_should_handle_type_error_on_load_json __________

self = <tests.test_tornadoparser.TestJSONArgs object at 0x7ff7fb4d0160>

    def test_it_should_handle_type_error_on_load_json(self):
        # but this is different from the test above where the payload was valid
        # and empty -- missing vs {}
        # NOTE: `event_loop` is the pytest-aiohttp event loop fixture, but it's
        # important to get an event loop here so that we can construct a future
        request = make_request(
>           body=tornado.concurrent.Future(),
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
            headers={"Content-Type": "application/json"},
        )

tests/test_tornadoparser.py:158: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <asyncio.unix_events._UnixDefaultEventLoopPolicy object at 
0x7ff7fcb6c440>

    def get_event_loop(self):
        """Get the event loop for the current context.
    
        Returns an instance of EventLoop or raises an exception.
        """
        if self._local._loop is None:
>           raise RuntimeError('There is no current event loop in thread %r.'
                               % threading.current_thread().name)
E           RuntimeError: There is no current event loop in thread 'MainThread'.

/usr/lib/python3.14/asyncio/events.py:715: RuntimeError
=========================== short test summary info ============================
FAILED 
tests/test_tornadoparser.py::TestJSONArgs::test_it_should_handle_type_error_on_load_json
=================== 1 failed, 453 passed, 3 skipped in 0.98s ===================
E: pybuild pybuild:485: test: plugin pyproject failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_webargs/build; python3.14 -m pytest -k 
'not test_get_path_param and not test_get_with_no_json_body and not test_post 
and not test_missing_required_field_throws_422 and not 
test_required_field_provided and not test_use_kwargs_with_error and not 
test_user_validator_returns_422_by_default'
I: pybuild base:385: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_webargs/build; 
python3.13 -m pytest -k 'not test_get_path_param and not 
test_get_with_no_json_body and not test_post and not 
test_missing_required_field_throws_422 and not test_required_field_provided and 
not test_use_kwargs_with_error and not 
test_user_validator_returns_422_by_default'
============================= test session starts ==============================
platform linux -- Python 3.13.12, pytest-9.0.3, pluggy-1.6.0
rootdir: /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_webargs/build
configfile: pyproject.toml
plugins: asyncio-1.4.0, typeguard-4.4.4
asyncio: mode=Mode.STRICT, debug=False, 
asyncio_default_fixture_loop_scope=None, 
asyncio_default_test_loop_scope=function
collected 457 items

tests/test_bottleparser.py ........................................s     [  8%]
tests/test_core.py ..................................................... [ 20%]
........................................................................ [ 36%]
..............                                                           [ 39%]
tests/test_djangoparser.py ........................................s.... [ 49%]
.                                                                        [ 49%]
tests/test_falconparser.py .....................................s....... [ 59%]
......                                                                   [ 60%]
tests/test_flaskparser.py .............................................. [ 70%]
..........................................................               [ 83%]
tests/test_pyramidparser.py ...........................................  [ 92%]
tests/test_tornadoparser.py ............F....................            [100%]

=================================== FAILURES ===================================
__________ TestJSONArgs.test_it_should_handle_type_error_on_load_json __________

self = <tests.test_tornadoparser.TestJSONArgs object at 0x7f1f4ce52cf0>

    def test_it_should_handle_type_error_on_load_json(self):
        # but this is different from the test above where the payload was valid
        # and empty -- missing vs {}
        # NOTE: `event_loop` is the pytest-aiohttp event loop fixture, but it's
        # important to get an event loop here so that we can construct a future
        request = make_request(
>           body=tornado.concurrent.Future(),
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
            headers={"Content-Type": "application/json"},
        )

tests/test_tornadoparser.py:158: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <asyncio.unix_events._UnixDefaultEventLoopPolicy object at 
0x7f1f4cef5160>

    def get_event_loop(self):
        """Get the event loop for the current context.
    
        Returns an instance of EventLoop or raises an exception.
        """
        if (self._local._loop is None and
                not self._local._set_called and
                threading.current_thread() is threading.main_thread()):
            stacklevel = 2
            try:
                f = sys._getframe(1)
            except AttributeError:
                pass
            else:
                # Move up the call stack so that the warning is attached
                # to the line outside asyncio itself.
                while f:
                    module = f.f_globals.get('__name__')
                    if not (module == 'asyncio' or 
module.startswith('asyncio.')):
                        break
                    f = f.f_back
                    stacklevel += 1
            import warnings
            warnings.warn('There is no current event loop',
                          DeprecationWarning, stacklevel=stacklevel)
            self.set_event_loop(self.new_event_loop())
    
        if self._local._loop is None:
>           raise RuntimeError('There is no current event loop in thread %r.'
                               % threading.current_thread().name)
E           RuntimeError: There is no current event loop in thread 'MainThread'.

/usr/lib/python3.13/asyncio/events.py:716: RuntimeError
=========================== short test summary info ============================
FAILED 
tests/test_tornadoparser.py::TestJSONArgs::test_it_should_handle_type_error_on_load_json
=================== 1 failed, 453 passed, 3 skipped in 1.01s ===================
E: pybuild pybuild:485: test: plugin pyproject failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_webargs/build; python3.13 -m pytest -k 
'not test_get_path_param and not test_get_with_no_json_body and not test_post 
and not test_missing_required_field_throws_422 and not 
test_required_field_provided and not test_use_kwargs_with_error and not 
test_user_validator_returns_422_by_default'
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.14 
3.13" --parallel=2 returned exit code 13
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
Source: python-webargs
Source-Version: 8.7.1-2
Done: Edward Betts <[email protected]>

We believe that the bug you reported is fixed in the latest version of
python-webargs, 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.
Edward Betts <[email protected]> (supplier of updated python-webargs 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, 16 Jun 2026 17:21:05 +0100
Source: python-webargs
Architecture: source
Version: 8.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Edward Betts <[email protected]>
Closes: 1139417
Changes:
 python-webargs (8.7.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix Tornado future test to create an explicit event loop.
     (Closes: #1139417)
Checksums-Sha1:
 f78ccc7e8074722226f99b4810f4979394aa3287 2327 python-webargs_8.7.1-2.dsc
 4a566ea81c24f217ad8d52a19dcd67cc3ab4c432 5216 
python-webargs_8.7.1-2.debian.tar.xz
 6499ba55e1f80cdb0fe205ecc82b4c70c344edb4 9335 
python-webargs_8.7.1-2_source.buildinfo
Checksums-Sha256:
 bae80452d8352ec983f4cab81705007454315c0f52bc92523f3191ca66460b61 2327 
python-webargs_8.7.1-2.dsc
 c023f00d5789ca1d1211d6541b08d736dbf6c469b30a0288c238453f556f61cb 5216 
python-webargs_8.7.1-2.debian.tar.xz
 34d2b4c8034cb083651bc6c85ae396295db2b956dd89f1cf15f284a747b6006d 9335 
python-webargs_8.7.1-2_source.buildinfo
Files:
 2ff240f5765985a99ac5e2c6d30e1d1c 2327 python optional 
python-webargs_8.7.1-2.dsc
 7c121d521f9902b5e6fadbf3ef30776e 5216 python optional 
python-webargs_8.7.1-2.debian.tar.xz
 dcfc5674292955aee008ac3f6d98b0d2 9335 python optional 
python-webargs_8.7.1-2_source.buildinfo

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

iQIzBAEBCgAdFiEE+4rPp4xyYInDitAmlgWhCYxjuSoFAmoxeMoACgkQlgWhCYxj
uSpNmg/+P0YfRpLnsaMwgeGeHnT5QdPPU17Z0oM8GthD2xfmDCXEk64BxXKzO9V+
OW/OpjorBb0DR40JM8hVYgS/9JIMYnWyXviLAb6VXE5UVIqI7yR7gIEV3jPVhgO2
NhE/wwGIUxVI/fQ0yFixkivRV+ClKmslRzkmCWy3/Dk7YK9UQaYNPOr7LqUtrOYt
izeZxTrEjyVnkdYajaf36fpb9UU75HlXIYq9rbp6FEGEOwDW6Is9OWi9C6bwjBbU
QuLTx/raCJjCW435+sOqfQZrOHp5GT6H4hHbS74gA/HO51tWM/5iZEzBD+A77C9g
AaYe2e4hvklMAe7j7JZfE8J9WOYA2ukTJhAqzsmowyAvHypi5oSLyEzANFXHddqy
nZlhNkMuq2gmvFqR7ICvPJLqmbqkN+I05FZmLhxCwcsNUFCTvaHhp4/1PVpMyfBg
jP/+D6REMcBgTWzqrb2b/52ayi5Uif3IsLyV6hqMxisLWrbiiypR/QRYYQjVn0Q8
zVAnQnK8owmpLDAMYSvjYbTvmNyiKMtjK2KFAKgYikymbsFX4YDdVRhECCyXAjcd
60HyZKVDHdt/FgwOcBaEWKyV6Pr6yZe7Pr7fUiJY0yXThWvtI9mXbgS9pFswdpkS
U/Hu+MnTvE0ACtWBYz8rojB2trmz4X3FWUxATOW7/xuTbeC07G4=
=aTGl
-----END PGP SIGNATURE-----

Attachment: pgpjGZs6crv0t.pgp
Description: PGP signature


--- End Message ---

Reply via email to