#1146864 caio: FTBFS on armhf, i386, loong64, ppc64el, s390x: failed tests

Package:
src:caio
Source:
src:caio
Submitter:
Sebastian Ramacher
Date:
2026-09-10 01:47:01 UTC
Severity:
normal
Tags:
#1146864#5
Date:
2026-09-06 12:52:29 UTC
From:
To:
Source: caio
Version: 0.12.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-arm@lists.debian.org, debian-loongarch@lists.debian.org, debian-powerpc@lists.debian.org, debian-s390@lists.debian.org, sramacher@debian.org
User: debian-s390@lists.debian.org
Usertags: s390x
User: debian-loongarch@lists.debian.org
Usertags: loong64
User: debian-powerpc@lists.debian.org
Usertags: ppc64el
User: debian-arm@lists.debian.org
Usertags: armhf
User: debian-qa@lists.debian.org
Usertags: i386

Dear maintainer,

caio FTBFS on armhf, i386, loong64, ppc64el and s390x with various test
failures:

=================================== FAILURES ===================================
______ test_write_operation_properties_before_submission[caio.thread_aio] ______

backend = <module 'caio.thread_aio' from '/build/reproducible-path/caio-0.12.3/.pybuild/cpython3_3.14_caio/build/caio/thread_aio.cpython-314-i386-linux-gnu.so'>

    def test_write_operation_properties_before_submission(backend):
        """.fileno/.offset/.nbytes/.payload for a freshly constructed write
        Operation must reflect the constructor arguments identically across
        every backend, even before it's ever submitted - unlike read (see
        below), nothing here depends on backend-specific buffer allocation
        strategy."""
        with tempfile.NamedTemporaryFile() as f:
            fd = f.fileno()
            payload = b"the quick brown fox"
            op = backend.Operation.write(payload, fd, 7)

            assert op.fileno == fd
            assert op.offset == 7

tests/test_aio_context.py:48: AssertionError
tests/test_aio_context.py:64: AssertionError
tests/test_raw_low_level.py:294: AssertionError
tests/test_raw_low_level.py:294: AssertionError
tests/test_raw_low_level.py:294: AssertionError
=============================== warnings summary ===============================
tests/test_asyncio_adapter.py:35: 13 warnings
  /build/reproducible-path/caio-0.12.3/.pybuild/cpython3_3.14_caio/build/tests/test_asyncio_adapter.py:35: DeprecationWarning: 'asyncio.iscoroutinefunction' is deprecated and slated for removal in Python 3.16; use inspect.iscoroutinefunction() instead
    if not asyncio.iscoroutinefunction(func):

#1146864#10
Date:
2026-09-06 12:57:56 UTC
From:
To:
Hello!


This is already fixed in the 0.12.3-2~exp1 which is uploaded in the
experimental for now
Please see
https://buildd.debian.org/status/package.php?p=caio&suite=experimental&pow_referer=

06.09.2026 16:52, Sebastian Ramacher пишет:

#1146864#15
Date:
2026-09-06 12:57:56 UTC
From:
To:
Hello!


This is already fixed in the 0.12.3-2~exp1 which is uploaded in the
experimental for now
Please see
https://buildd.debian.org/status/package.php?p=caio&suite=experimental&pow_referer=

06.09.2026 16:52, Sebastian Ramacher пишет:

#1146864#20
Date:
2026-09-06 13:00:18 UTC
From:
To:
Hi

Any reason that it hasn't been uploaded to unstable? We need to rebuild
caio for Python 3.13 removal in unstable.

Cheers

#1146864#31
Date:
2026-09-06 13:06:31 UTC
From:
To:
06.09.2026 17:00, Sebastian Ramacher пишет:

I'm working with xiao sheng wen on this (CCed).

The main problem here is that I have no time currently to update d/watch
to v5 together with optional fields in latest standard because of
breakage of my upstream CI.

#1146864#36
Date:
2026-09-09 18:58:29 UTC
From:
To:
There is no need to fix all issues in one upload, doing multiple uploads
to unstable for different fixes is fine (especially for a package with
such a short build time).

cu
Adrian

#1146864#41
Date:
2026-09-10 01:45:40 UTC
From:
To:
Hi,

在 2026/9/10 02:58, Adrian Bunk 写道:

The caio package had uploaded to mentors.d.n,

https://mentors.debian.net/package/caio/

Welcome to review and upload.

The following is the email about my review and our discuss before:
---------------------------------- New upload will into Debian new release -- Debian 14 forky in the next year. Debian 14 use new standard, so the new upload package should obey it. For keep the compatibility for old Debian 12 and Ubuntu 24.04, you may use git branch to do it. Please see: https://dep-team.pages.debian.net/deps/dep14/
------------------------------------- In fact, fix these lintian outputs is easy. Use git branch to maintain package also used much in https://salsa.debian.org. The salsa also support CI. Regards,