Package: src:uvloop
Version: 0.21.0+ds1-2
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.13 setup.py clean
running clean
removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/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.13 setup.py config /usr/lib/python3/dist-packages/setuptools/__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build build_ext --use-system-libuv
/usr/lib/python3/dist-packages/setuptools/__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/_version.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/_noop.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/_testbase.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
running egg_info
creating uvloop.egg-info
writing uvloop.egg-info/PKG-INFO
writing dependency_links to uvloop.egg-info/dependency_links.txt
writing requirements to uvloop.egg-info/requires.txt
writing top-level names to uvloop.egg-info/top_level.txt
writing manifest file 'uvloop.egg-info/SOURCES.txt'
Compiling uvloop/loop.pyx because it changed.
[1/1] Cythonizing uvloop/loop.pyx
reading manifest file 'uvloop.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*' under directory 'vendor/libuv'
warning: no previously-included files matching '*' found under directory 'vendor/libuv/.git'
warning: no previously-included files matching '*' found under directory 'vendor/libuv/docs'
warning: no previously-included files matching '*' found under directory 'vendor/libuv/img'
adding license file 'LICENSE-APACHE'
adding license file 'LICENSE-MIT'
writing manifest file 'uvloop.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'uvloop.handles' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'uvloop.handles' 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 'uvloop.handles' 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 'uvloop.handles' to be distributed and are
already explicitly excluding 'uvloop.handles' 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 'uvloop.includes' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'uvloop.includes' 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 'uvloop.includes' 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 'uvloop.includes' to be distributed and are
already explicitly excluding 'uvloop.includes' 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 uvloop/cbhandles.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/cbhandles.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/dns.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/errors.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/loop.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/loop.pyi -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/loop.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/lru.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/pseudosock.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/py.typed -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/request.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/request.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/server.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/server.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/sslproto.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
copying uvloop/sslproto.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles copying uvloop/handles/async_.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/async_.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/basetransport.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/basetransport.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/check.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/check.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/fsevent.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/fsevent.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/handle.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/handle.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/idle.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/idle.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/pipe.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/pipe.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/poll.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/poll.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/process.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/process.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/stream.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/stream.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/streamserver.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/streamserver.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/tcp.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/tcp.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/timer.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/timer.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/udp.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
copying uvloop/handles/udp.pyx -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/handles
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes copying uvloop/includes/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/consts.pxi -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/debug.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/flowcontrol.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/python.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/stdlib.pxi -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/system.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
copying uvloop/includes/uv.pxd -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/includes
running build_ext
building 'uvloop.loop' extension
creating build/temp.linux-x86_64-cpython-313/uvloop
x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/
python3.13 -c uvloop/loop.c -o build/temp.linux-x86_64-cpython-313/uvloop/loop.o -O2
x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-cpython-313/uvloop/loop.o -L/usr/lib/x86_64-linux-gnu -luv -lrt -lpthread -o /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/loop.cpython-313-x86_
64-linux-gnu.so
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build; python3.13 -m pytest -s tests --ignore=tests/test_pipes.py --ignore=tests/test_sourcecode.py --ignore=tests/test_sockets.py --ignore=tests/test_tcp.py --ignore=tests/test_libuv_
api.py --ignore=tests/test_dns.py
============================= test session starts ==============================
platform linux -- Python 3.13.2, pytest-8.3.5, pluggy-1.5.0
rootdir: /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build
configfile: pyproject.toml
plugins: typeguard-4.4.2
collected 296 items

tests/test_aiohttp.py ...s
tests/test_base.py .s............................................s................................F.......
tests/test_context.py ..................s..s.s......
tests/test_cython.py .
tests/test_dealloc.py .
tests/test_executors.py ....
tests/test_fs_event.py ..
tests/test_process.py ..................................................................................
tests/test_process_spawning.py .
tests/test_regr1.py .
tests/test_runner.py ..
tests/test_signals.py .....................
tests/test_testbase.py ...
tests/test_udp.py ..................ss...
tests/test_unix.py ..................................

=================================== FAILURES ===================================
________________________ TestBaseAIO.test_set_task_name ________________________
Traceback (most recent call last):
File "/usr/lib/python3.13/unittest/case.py", line 58, in testPartExecutor
yield
File "/usr/lib/python3.13/unittest/case.py", line 651, in run
self._callTestMethod(testMethod)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/usr/lib/python3.13/unittest/case.py", line 606, in _callTestMethod
if method() is not None:
~~~~~~^^
File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/tests/test_base.py", line 594, in test_set_task_name
self.assertEqual(result, "mytask!")
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/unittest/case.py", line 907, in assertEqual
assertion_func(first, second, msg=msg)
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/unittest/case.py", line 900, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: None != 'mytask!'
=============================== warnings summary ===============================
tests/test_aiohttp.py::Test_UV_AioHTTP::test_aiohttp_graceful_shutdown
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/tests/test_aiohttp.py:85: NotAppKeyWarning: It is recommended to use web.AppKey instances for keys.
https://docs.aiohttp.org/en/stable/web_advanced.html#application-s-config
app['websockets'] = weakref.WeakSet()

tests/test_aiohttp.py::Test_UV_AioHTTP::test_aiohttp_graceful_shutdown
/usr/lib/python3/dist-packages/aiohttp/web_runner.py:95: DeprecationWarning: shutdown_timeout should be set on BaseRunner
super().__init__(

tests/test_base.py::TestBaseAIO::test_shutdown_asyncgens_01
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build/uvloop/_testbase.py:113: RuntimeWarning: coroutine '_TestBase.test_set_task_name.<locals>.coro' was never awaited
gc.collect()
Enable tracemalloc to get traceback where the object was allocated.
See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

tests/test_executors.py::TestUVExecutors::test_executors_process_pool_01 tests/test_executors.py::TestAIOExecutors::test_executors_process_pool_01 tests/test_regr1.py::TestIssue39Regr::test_issue39_regression
/usr/lib/python3.13/multiprocessing/popen_fork.py:67: DeprecationWarning: This process (pid=95308) is multi-threaded, use of fork() may lead to deadlocks in the child.
self.pid = os.fork()

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info ============================
FAILED tests/test_base.py::TestBaseAIO::test_set_task_name - AssertionError: ...
============ 1 failed, 287 passed, 8 skipped, 6 warnings in 37.87s =============
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_uvloop/build; python3.13 -m pytest -s tests --ignore=tests/test_pipes.py --ignore=tests/test_sourcecode.py --ignore=tests/test_sockets.py -
-ignore=tests/test_tcp.py --ignore=tests/test_libuv_api.py --ignore=tests/test_dns.py
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13
make: *** [debian/rules:13: 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/202503/

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

Thanks.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

tags 1101258 patch

Bug #1101258 [src:uvloop] uvloop: FTBFS: AssertionError: None != 'mytask!' Added tag(s) patch.

--
1101258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101258
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Control: tags 1101258 patch

This is actually caused by a test that makes assumsations about the
builtin python asyncio event loops that no longer hold.

python upstream commit https://github.com/python/cpython/commit/38a99568763604ccec5d5027f0658100ad76876f
semi-silently moved the responsibity for managing a task name from
create_task method to the __init__ of the Task class.

This 3.14 change was backported upstream to 3.13 in

https://github.com/python/cpython/commit/7b0543ebe649aea11531e994289293f23f41064e

The tests in uvloop fail with the new behavior.

The uvloop test suite runs the tests once using the uvloop implementation (which succeeds) and once (likely as validation) against python's asyncio implementation. The later run fails.

Thus this not a problem in the uvloop code. One way would be to disable
the test.

But it is also possible to work around the test problem by changing the
test to handle the chance only in the non uvloop case as this:


--- uvloop-0.21.0+ds1.orig/tests/test_base.py
+++ uvloop-0.21.0+ds1/tests/test_base.py
@@ -576,9 +576,14 @@ class _TestBase:
async def coro():
pass

- factory = lambda loop, coro, **kwargs: MyTask(
- coro, loop=loop, **kwargs
- )
+ def factory(loop, coro, **kwargs):
+ task = MyTask(coro, loop=loop, **kwargs)
+ # python moved the responsibility to set the name to the Task class constructor,
+ # so MyTask.set_name is never called by python's create_task.
+ # Compensate for that here
+ if self.is_asyncio_loop():
+ task.set_name(kwargs['name'])
+ return task

self.assertIsNone(self.loop.get_task_factory())
task = self.loop.create_task(coro(), name="mytask")


I hope some one can prepare a upload which either disables the test or with
a patch that fixes the test in the case it run with the python event loop.

Regards,
- Martin Hostettler

Processing control commands:

tag -1 pending

Bug #1101258 [src:uvloop] uvloop: FTBFS: AssertionError: None != 'mytask!' Added tag(s) pending.

--
1101258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101258
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Control: tag -1 pending

Hello,

Bug #1101258 in uvloop reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/uvloop/-/commit/2a974218fb44d14eb494bdaa2ee327e3e0fa3f21

------------------------------------------------------------------------ Compensate for asyncio changes in Python 3.13.3/3.14

Closes: #1101258 ------------------------------------------------------------------------

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/1101258

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Wed, 16 Apr 2025 11:19:55 +0000
with message-id <E1u50o7-00D2qj-5Z@fasolo.debian.org>
and subject line Bug#1101258: fixed in uvloop 0.21.0+ds1-3
has caused the Debian Bug report #1101258,
regarding uvloop: FTBFS: AssertionError: None != 'mytask!'
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 owner@bugs.debian.org
immediately.)


--
1101258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101258
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 25 Mar 2025 00:11:54 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-121.1 required=4.0 tests=ALL_TRUSTED,BAYES_00,
BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC
autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 179; hammy, 150; neutral, 607; spammy,
0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--trixie,
0.000-+--pkgbuilddir, 0.000-+--PKGBUILDDIR, 0.000-+--sk:dh_auto Return-path: <sanvila@debian.org>
Received: from muffat.debian.org ([2607:f8f0:614:1::1274:33]:51804)
from C=NA,ST=NA,L=Ankh