Your message dated Sun, 30 Aug 2026 15:34:23 +0000
with message-id <[email protected]>
and subject line Bug#1144748: fixed in sqlalchemy 2.0.52+ds1-1
has caused the Debian Bug report #1144748,
regarding sqlalchemy: FTBFS against python 3.15rc1
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 [email protected]
immediately.)
--
1144748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144748
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sqlalchemy
Version: 2.0.48+ds1-1
User: [email protected]
Usertags: python3.15
Tags: patch
Hi!
While rebuilding the python related packages against the Python 3.15rc1
version we found that sqlalchemy fails to build from source [2]. The fix is
already release upstream with the version 2.0.50 (438f1f7 Adjust
TypeError message to Python 3.15), and in the release 2.0.52, version
3.15 was added as a officially supported.
I applied the upstream fix in the sandbox [1] to be able to build the
packages that depend on sqlalchemy, please consider either adding the
upstream patch or updating sqlalchemy to newer version so it support the
upcoming 3.15 version.
Happy hacking,
[1]: https://debusine.debian.net/debian/r-python-python3.15/
[2]:
https://debusine.debian.net/debian/r-python-python3.15/work-request/1013699/
--
"If you are in a hole, stop digging." -- The First Rule of Excavation
Saludos /\/\ /\ >< `/
diff -Nru sqlalchemy-2.0.48+ds1/debian/changelog
sqlalchemy-2.0.48+ds1/debian/changelog
--- sqlalchemy-2.0.48+ds1/debian/changelog 2026-03-26 17:21:23.000000000
+0100
+++ sqlalchemy-2.0.48+ds1/debian/changelog 2026-08-18 10:45:05.000000000
+0200
@@ -1,3 +1,11 @@
+sqlalchemy (2.0.48+ds1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport upstream patch: adjust-typeerror-message-to-py315.patch
+ Fix build against python 3.15
+
+ -- Maximiliano Curia <[email protected]> Tue, 18 Aug 2026 10:45:05 +0200
+
sqlalchemy (2.0.48+ds1-1) unstable; urgency=medium
* New upstream release
diff -Nru
sqlalchemy-2.0.48+ds1/debian/patches/adjust-typeerror-message-to-py315.patch
sqlalchemy-2.0.48+ds1/debian/patches/adjust-typeerror-message-to-py315.patch
---
sqlalchemy-2.0.48+ds1/debian/patches/adjust-typeerror-message-to-py315.patch
1970-01-01 01:00:00.000000000 +0100
+++
sqlalchemy-2.0.48+ds1/debian/patches/adjust-typeerror-message-to-py315.patch
2026-08-18 10:44:41.000000000 +0200
@@ -0,0 +1,68 @@
+commit 438f1f78492aae8577d97874d125af212d3da049
+Author: Karolina Surma <[email protected]>
+Date: Tue May 19 10:20:38 2026 -0400
+
+ Adjust TypeError message to Python 3.15
+
+ <!-- Provide a general summary of your proposed changes in the Title field
above -->
+
+ ### Description
+ The `.fromisoformat()` error message tested in `test_no_string()` changed
in Python 3.15, this fixes the test.
+
+ See #13308 for the `rel_2_0` branch.
+
+ ### Checklist
+ <!-- go over following points. check them with an `x` if they do apply,
(they turn into clickable checkboxes once the PR is submitted, so no need to do
everything at once)
+
+ -->
+
+ This pull request is:
+
+ - [ ] A documentation / typographical / small typing error fix
+ - Good to go, no issue or tests are needed
+ - [x] A short code fix (in a test, therefore I didn’t create an issue)
+ - please include the issue number, and create an issue if none
exists, which
+ must include a complete example of the issue. one line code
fixes without an
+ issue and demonstration will not be accepted.
+ - Please include: `Fixes: #<issue number>` in the commit message
+ - please include tests. one line code fixes without tests will
not be accepted.
+ - [ ] A new feature implementation
+ - please include the issue number, and create an issue if none
exists, which must
+ include a complete example of how the feature would look.
+ - Please include: `Fixes: #<issue number>` in the commit message
+ - please include tests.
+
+ **Have a nice day!**
+
+ Closes: #13307
+ Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/13307
+ Pull-request-sha: 90bc13fc416ea45ba5429d5f8ecffc24b108c1b1
+
+ Change-Id: I461d71b0fad18fa4f108102bb1c22c0e980fc70e
+ (cherry picked from commit f07ad99839105f254df4e640ab851bcc6910168c)
+
+diff --git a/test/engine/test_processors.py b/test/engine/test_processors.py
+index 4f06f772a..e2bb50a2c 100644
+--- a/test/engine/test_processors.py
++++ b/test/engine/test_processors.py
+@@ -73,13 +73,13 @@ class _DateProcessorTest(fixtures.TestBase):
+
+ eq_(self.module.str_to_date("2022-04-03"), datetime.date(2022, 4, 3))
+
+- def test_date_no_string(self):
+- assert_raises_message(
+- TypeError,
+- "fromisoformat: argument must be str",
+- self.module.str_to_date,
+- 2012,
+- )
++ @combinations("str_to_datetime", "str_to_time", "str_to_date")
++ def test_no_string(self, meth):
++ with expect_raises_message(
++ TypeError, r"fromisoformat.* argument must be str"
++ ):
++ fn = getattr(self.module, meth)
++ fn(2012)
+
+ def test_datetime_no_string_custom_reg(self):
+ assert_raises_message(
diff -Nru sqlalchemy-2.0.48+ds1/debian/patches/series
sqlalchemy-2.0.48+ds1/debian/patches/series
--- sqlalchemy-2.0.48+ds1/debian/patches/series 1970-01-01 01:00:00.000000000
+0100
+++ sqlalchemy-2.0.48+ds1/debian/patches/series 2026-08-18 10:44:41.000000000
+0200
@@ -0,0 +1 @@
+adjust-typeerror-message-to-py315.patch
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sqlalchemy
Source-Version: 2.0.52+ds1-1
Done: Piotr Ożarowski <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sqlalchemy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Piotr Ożarowski <[email protected]> (supplier of updated sqlalchemy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 30 Aug 2026 16:00:54 +0200
Source: sqlalchemy
Architecture: source
Version: 2.0.52+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski <[email protected]>
Changed-By: Piotr Ożarowski <[email protected]>
Closes: 1144748
Changes:
sqlalchemy (2.0.52+ds1-1) unstable; urgency=medium
.
* New upstream release (closes: 1144748)
* Use DEB_BUILD_OPTION_PARALLEL instead of `nproc`
Checksums-Sha1:
11d59087eea73bf2990a50abb7d726af3437ca1d 2438 sqlalchemy_2.0.52+ds1-1.dsc
a4e46e08fbb2e782d921ee4bdfad2b0b65992f21 3553632
sqlalchemy_2.0.52+ds1.orig.tar.xz
0cf153debb5cc6a90e00c8225edc2d0afa3d10db 14116
sqlalchemy_2.0.52+ds1-1.debian.tar.xz
4e37d452f80a8d016add43ff00755a83220c7874 9616
sqlalchemy_2.0.52+ds1-1_amd64.buildinfo
Checksums-Sha256:
3d782bdfd1a44508764b831a4294a958a0abe254053b79a33e3d018611519810 2438
sqlalchemy_2.0.52+ds1-1.dsc
6385e591e7adf9dc423dc3f0612b9dc74abae034bdb93f314352bb67fc8b7e5e 3553632
sqlalchemy_2.0.52+ds1.orig.tar.xz
0c418e100a0817e6a606a530b1919ea61b549d8b5322f49a8a2a4029f29fef3a 14116
sqlalchemy_2.0.52+ds1-1.debian.tar.xz
022da5974aa8e1085d9d10b7ddbd3925d971ae01073d5d64a10d5ffe1463960b 9616
sqlalchemy_2.0.52+ds1-1_amd64.buildinfo
Files:
20eed8ff80545e32a0730dceab512429 2438 python optional
sqlalchemy_2.0.52+ds1-1.dsc
e43ec6704bb147fd70ef86adc9be689a 3553632 python optional
sqlalchemy_2.0.52+ds1.orig.tar.xz
1dfad7bb109a509957f3cb052ed5dfd7 14116 python optional
sqlalchemy_2.0.52+ds1-1.debian.tar.xz
8f0fd38a0c578b3f94d6c10ec304139f 9616 python optional
sqlalchemy_2.0.52+ds1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAmqUSQcACgkQrvbxoqdF
dkU/gQ/+NmSBnzghoTV99U+7j6rKYH1XGFpBUSfJZthXXNYHHHnEDYcyjZGoHZyf
We5NAJSIxWfWsSdnFujj74alnc1F3EcZ/CNvVMu+oRAQDop/EIG1FFFkdComcwP5
wRY3e7Z7PXi1P8UDF7Jlti7xIuc+GKYfSlj9Lak1YmfSDHx3SpjagwEoaZcS5PV7
FyYx3lctJYSIQWltzPoClStDscF+EJCK7YXof79O6Dh5E9P++Vxq1VTkT699UdNE
O0LE6agnX2OZCY6pXX5bgwVHfew73t8TBoMdR9D3yQ8VXv9png/WHlVgdt8qP7Gk
R9Oeyyu4KbGmNK4m0IuTLXAo70j1RfeUEx1uM2ZlGFV8CzXCUA0sgADsfDK6gO8e
qiXObxpbIF60H7KPX7ivVANPfs9ebhsaN3DS2bcRrKWyARE+u/lfi6+dNsQNcUqJ
7Wd3sgq2UAMm251RT24O5SMXN6MawVk33jkLDnFxYEcnnfPRHRpnodNMk218xSUY
3+rn6OWcrehJOe7xQ449z9pXK8R463Cv5U7FWi5btDtAQWtAkritcc804hu/ozL6
7DFd1RhIQshOuWynGbZRYLT1K6HxhJkJGVI5PhJUmy8yw0zWYwaesyJcbC5EU5wf
gx7r5xEMFt5O4i7sYclP5qdlP/ztVpMIrq1NypVy7RvZTTFrIHI=
=AFWZ
-----END PGP SIGNATURE-----
pgp_R6RYkGXbI.pgp
Description: PGP signature
--- End Message ---
