Source: pyodbc Version: 5.1.0-1 Severity: normal Tags: patch upstream User: debian-pyt...@lists.debian.org Usertags: python3.13 Forwarded: https://github.com/mkleehammer/pyodbc/issues/1344
This package failed build from source when test-built against a version of python3-defaults that incudes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html Log snippet: 111 | PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v, | ^~~~~~~~~~~~~~~~~~~ src/params.cpp:480:38: error: too few arguments to function ‘int _PyLong_AsByteArray(PyLongObject*, unsigned char*, size_t, int, int, int)’ 480 | int ret = _PyLong_AsByteArray((PyLongObject*)digitLong, pNum->val, sizeof(pNum->val), 1, 0); | ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/include/python3.13/cpython/longobject.h:111:17: note: declared here 111 | PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v, | ^~~~~~~~~~~~~~~~~~~ error: command '/usr/bin/aarch64-linux-gnu-g++' failed with exit code 1 ... dh_auto_build: error: pybuild --build -i python{version} -p "3.13 3.12" returned exit code 13 make: *** [debian/rules:11: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -------------------------------------------------------------------------------- Build finished at 2024-09-11T15:14:31Z If required, the full build log is available here (for the next 30 days): https://debusine.debian.net/artifact/700923/ This bug has been filed at "normal" severity, as we haven't started the transition to add 3.13 as a supported version, yet. This will be raised to RC as soon as that happens, hopefully well before trixie. Thanks, Stefano
