Package: src:twine
Version: 6.2.0-5
Severity: serious
Tags: ftbfs forky sid

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/202608/

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

Thanks.

--------------------------------------------------------------------------------
[...]
=================================== FAILURES ===================================
_________________________ test_fails_rst_syntax_error __________________________

tmp_path = 
PosixPath('/tmp/pytest-of-sbuild/pytest-0/test_fails_rst_syntax_error0')
capsys = <_pytest.capture.CaptureFixture object at 0x7f9def26c550>
caplog = <_pytest.logging.LogCaptureFixture object at 0x7f9def6674d0>

    def test_fails_rst_syntax_error(tmp_path, capsys, caplog):
        sdist = build_sdist_with_metadata(
            tmp_path,
            """\
            Metadata-Version: 2.1
            Name: test-package
            Version: 1.2.3
            Description-Content-Type: text/x-rst
    
    
            ============
    
            """,
        )
    
        assert check.check([sdist])
    
        assert capsys.readouterr().out == f"Checking {sdist}: FAILED\n"
    
>       assert caplog.record_tuples == [
            (
                "twine.commands.check",
                logging.ERROR,
                "`long_description` has syntax errors in markup "
                "and would not be rendered on PyPI.\n"
                "line 2: Warning: Document or section may not begin with a 
transition.",
            ),
        ]
E       AssertionError: assert [('twine.comm...e document.')] == 
[('twine.comm...transition.')]
E         
E         At index 0 diff: ('twine.commands.check', 40, '`long_description` has 
syntax errors in markup and would not be rendered on PyPI.\nline 2: Warning: 
Transition at the end of the document.') != ('twine.commands.check', 40, 
'`long_description` has syntax errors in markup and would not be rendered on 
PyPI.\nline 2: Warning: Document or section may not begin with a transition.')
E         Use -v to get more diff

tests/test_check.py:116: AssertionError
----------------------------- Captured stderr call -----------------------------
`long_description` has syntax errors in markup and would not be rendered on 
PyPI.
line 2: Warning: Transition at the end of the document.
------------------------------ Captured log call -------------------------------
ERROR    twine.commands.check:check.py:147 `long_description` has syntax errors 
in markup and would not be rendered on PyPI.
line 2: Warning: Transition at the end of the document.
=========================== short test summary info ============================
FAILED tests/test_check.py::test_fails_rst_syntax_error - AssertionError: ass...
=================== 1 failed, 225 passed, 3 skipped in 0.54s ===================
E: pybuild pybuild:485: test: plugin pyproject failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_twine/build; python3.14 -m pytest 
--ignore tests/test_integration.py
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.14 
--test-pytest --test-args "--ignore tests/test_integration.py" --parallel=2 
returned exit code 13
make[1]: *** [debian/rules:22: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:5: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

Reply via email to