Your message dated Fri, 4 Apr 2025 10:53:17 +0200
with message-id
<wh2kkv7aoux7xrvb4n5dsvq4253bijkyea6oqpfgcp6ustfj4p@do2iwck44nwg>
and subject line fixed in latest upstream release
has caused the Debian Bug report #1101868,
regarding sqlalchemy: FTBFS: 6 tests failed
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 ow...@bugs.debian.org
immediately.)
--
1101868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sqlalchemy
Version: 2.0.32+ds1-1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
SKIPPED [1] lib/sqlalchemy/testing/config.py:423:
'test/orm/dml/test_update_delete_where.py::UpdateDeleteTest_sqlite+pysqlite_3_46_1::test_update_against_external_non_mapped_cols
(call)' : not postgresql and not mssql
SKIPPED [1] lib/sqlalchemy/testing/config.py:423:
'test/base/test_utils.py::CyExtensionTest::test_all_cyext_imported (call)' : No
Cython
SKIPPED [1] lib/sqlalchemy/testing/config.py:423:
'test/orm/test_versioning.py::ServerVersioningTest_sqlite+pysqlite_3_46_1::test_concurrent_mod_err_expire_on_commit
(call)' : sqlite
SKIPPED [1] lib/sqlalchemy/testing/config.py:423:
'test/orm/test_versioning.py::ServerVersioningTest_sqlite+pysqlite_3_46_1::test_concurrent_mod_err_noexpire_on_commit
(call)' : sqlite
SKIPPED [1] lib/sqlalchemy/testing/config.py:423:
'test/orm/test_versioning.py::VersioningTest_sqlite+pysqlite_3_46_1::test_versioncheck_for_update
(call)' : no FOR UPDATE NOWAIT support
FAILED
test/orm/declarative/test_tm_future_annotations.py::MappedColumnTest::test_extract_pep593_from_pep695[typekeyword]
FAILED
test/orm/declarative/test_tm_future_annotations.py::MappedColumnTest::test_pep695_literal_defaults_to_enum
FAILED
test/orm/declarative/test_tm_future_annotations_sync.py::MappedColumnTest::test_extract_pep593_from_pep695[typekeyword]
FAILED
test/orm/declarative/test_tm_future_annotations_sync.py::MappedColumnTest::test_pep695_literal_defaults_to_enum
FAILED
test/orm/declarative/test_typed_mapping.py::MappedColumnTest::test_extract_pep593_from_pep695[typekeyword]
FAILED
test/orm/declarative/test_typed_mapping.py::MappedColumnTest::test_pep695_literal_defaults_to_enum
= 6 failed, 21393 passed, 10842 skipped, 55 deselected, 1 warning in 1630.46s
(0:27:10) =
make[1]: *** [debian/rules:20: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:11: binary] Error 2
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/202504/
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:sqlalchemy, so that this is still
visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: sqlalchemy
Source-Version: 2.0.40+ds1-1
Fixed upstream
--- End Message ---
