Your message dated Sat, 30 May 2026 21:35:46 +0000
with message-id <[email protected]>
and subject line Bug#1138490: fixed in python-xmlsec 1.3.17-1
has caused the Debian Bug report #1138490,
regarding please update to current 1.3.17
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.)
--
1138490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1138490
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-xmlsec
Version: 1.3.14-3
Severity: important
X-Debbugs-Cc: [email protected]
Hi,
unstable contains 1.3.14 which is from Apr, 17 2024.
Since then
1.3.17 Latest
Release Date: 2025-11-11
Version: 1.3.17
[...]
1.3.16
Release Date: 2025-07-10
Version: 1.3.16
[...]
1.3.15
What's Changed
Explicitly cast the pointer type in PyXmlSec_ClearReplacedNodes by @hroncok in
#325
Fix sdist CI workflow by @jonathangreen in #330
Build wheels for Python 3.13 by @jonathangreen in #329
Fix linuxbrew workflow by @jonathangreen in #331
Fix macosx CI workflow by @jonathangreen in #332
Fix type mismatch in PyXmlSec_ClearReplacedNodes for Python 3.13 compatibility
by @haya4ux in #340
New Contributors
@hroncok made their first contribution in #325
@haya4ux made their first contribution in #340
Full Changelog: 1.3.14...1.3.15
happened.
#325 is included in a patch, though.
I stumbled upon this since python-xmlsec as of now fails in the tests with
xmlsec1 1.3.11 from experimental.
https://github.com/lsh123/xmlsec/pull/1104#issuecomment-4462370741 suggests a
patch which doesn't apply on 1.3.14 but on 1.3.17.
(That patch still makes it fail here with xmlsec 1.3.11, but that's for an
other bug proably, it at least would help for further steps if python-xmlsec
was 1.3.17 anyway.)
Already did a local upgrade here and looks fine and straightforward.
I could do a team upload but I am not member of the DPMT :)
rene@frodo:~$ ratt -dist unstable -chdist sid -sbuild_dist unstable
-direct-rdeps python-xmlsec_1.3.17-1_amd64.changes
2026/05/30 19:49:26 Loading changes file "python-xmlsec_1.3.17-1_amd64.changes"
2026/05/30 19:49:26 - 2 binary packages: python3-xmlsec python3-xmlsec-dbgsym
2026/05/30 19:49:26 Corresponding .debs (will be injected when building):
2026/05/30 19:49:26 python3-xmlsec-dbgsym_1.3.17-1_amd64.deb
2026/05/30 19:49:26 python3-xmlsec_1.3.17-1_amd64.deb
2026/05/30 19:49:26 Using --depth=2 for dose-ceve(1) reverse dependency closure
2026/05/30 19:49:26 Figuring out reverse build dependencies using dose-ceve(1).
This might take a while
2026/05/30 19:50:27 Found 1 reverse build dependencies
2026/05/30 19:50:27 Warning: could not resolve Suite for "unstable": no suite
found for codename "unstable" (no -updates/-security overlays)
2026/05/30 19:50:27 Building package 1 of 1: python3-onelogin-saml2
2026/05/30 19:51:38 Completed building 1 packages with 1 workers
2026/05/30 19:51:38 Build results:
2026/05/30 19:51:38 PASSED: python3-onelogin-saml2
Regards,
Rene
--- End Message ---
--- Begin Message ---
Source: python-xmlsec
Source-Version: 1.3.17-1
Done: Alexandre Detiste <[email protected]>
We believe that the bug you reported is fixed in the latest version of
python-xmlsec, 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.
Alexandre Detiste <[email protected]> (supplier of updated python-xmlsec 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: Sat, 30 May 2026 22:59:12 +0200
Source: python-xmlsec
Architecture: source
Version: 1.3.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Alexandre Detiste <[email protected]>
Closes: 1138490
Changes:
python-xmlsec (1.3.17-1) unstable; urgency=medium
.
* Team upload.
* New upstream version 1.3.17 (Closes: #1138490)
* Drop patch applied upstream
* Switch to pybuild-plugin-pyproject
* Add debian/salsa-ci.yml
* Add debian/upstream/metadata
* Rewrite d/watch in v5 format
* Bump Standards-Version to 4.7.4, drop Priority: tag
Checksums-Sha1:
fe6a774beba49d887ec5d9c12e8559d0062b71fa 2279 python-xmlsec_1.3.17-1.dsc
eb6682cc642cbb9c9079536edcd0705ddb64c6a6 115637
python-xmlsec_1.3.17.orig.tar.gz
1db3df65ddfd35341d17afb247fade551efe80c8 2800
python-xmlsec_1.3.17-1.debian.tar.xz
19dd961c82de4089b0a8f8facd3cc994ba77cd57 8992
python-xmlsec_1.3.17-1_source.buildinfo
Checksums-Sha256:
c4e7ffc3799cce0706d2676d80e5fceead3ded2fc8d8adfd8d6aaa501cd44020 2279
python-xmlsec_1.3.17-1.dsc
f3fac9ae679f66585925cc00c5f6839ae36c1d03157619571dee18acc05b9c01 115637
python-xmlsec_1.3.17.orig.tar.gz
6471534ce98101bd8ab6a3d0d103cab0d1e3c58f1c3dd1c7128243221c3bb2b0 2800
python-xmlsec_1.3.17-1.debian.tar.xz
7754e9da9a9e6498db4d80b20de089af8a8f04b9415dc16a1e28322f72646f69 8992
python-xmlsec_1.3.17-1_source.buildinfo
Files:
1ec67962533f85f837953853116e87e0 2279 python optional
python-xmlsec_1.3.17-1.dsc
8e9b9c7f2c872e1839b7ee948e733616 115637 python optional
python-xmlsec_1.3.17.orig.tar.gz
180cccfc3ff8d579d69949c1a9d27f5c 2800 python optional
python-xmlsec_1.3.17-1.debian.tar.xz
f39452b7ebd0089951c3cda8ed07028a 8992 python optional
python-xmlsec_1.3.17-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmobUiwRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBp5Vw//XQjt2Hw5evkVQ3jHkiOHtGO36BDcwWeG
2AqOLPEgeMT27ZiWtIKgDKEMNvlJzK42IqCUgm4yg6L6D9txJRKDAre9mSIZsUdk
gFddJw1K8BMyvfTN7UzgWOaKfG5KD11YMHDGCzF2PlEZbKXHJEMH1PjT97rrUkKi
GATblsMHH37tf1vQ21qM7c00wb6gCFUq1MBhVI3mpEOxRjFeUNCTJ8kVs4HPuaMg
FktJq+YqK/baHstV22s8dz7ge85wuMrDZCo62EInlr1WdQ3/jmEwSCJURWKXHV6d
Y26PyfyAlfZMy5B8kmBz+8TgA1BzOzMcE/KllKB0Cd+mcLeFRF8xwyyFT6GWHqbL
AzrVtWaAl3c3xnIpO2pHL7abEnYTDdsBDljacNlrV4PoidTtGtRnuPhQIgnFIN3Y
mu+osP4/NU8RX0zpwVczFmgsQghyiHwhigaZ80SMHP+/XbzuMzZl1vPbGMiIQVPS
mA9L2pmSTUsBKp6QMYCOlMv4uichzpLyxmF4tbLJ+jnVtsOcTcziEAqa4uWjiQM2
vEtANNO+IlS5osTSsAJV8kxiA/px0bd0vwItsCNs5rR2YKBxB6Ot85vSMgAP5oWf
3u5nxl2ZH69ftXlrij8mxu3E1TpbNv+ZXoXUYYH65J8uEPlCgei+t30Y7zLK0nYH
OzFq2JfSvA0=
=grHe
-----END PGP SIGNATURE-----
pgp0IbB4sORJD.pgp
Description: PGP signature
--- End Message ---
