Followup-For: Bug #859572 X-Debbugs-Cc: solo-debianb...@goeswhere.com, bugs-debian-20170...@james-ross.co.uk Control: reassign -1 libxml2 Control: affects -1 libxslt1.1 xsltproc Control: forwarded -1 https://gitlab.gnome.org/GNOME/libxslt/-/issues/37 Control: tags -1 fixed-upstream Control: fixed -1 libxml2/2.9.12+dfsg-1 Control: close -1
This doesn't appear reproducible anymore, and after tracing back to figure out when the fix for it landed, it was somewhere between bookworm and bullseye. That helped to narrow down the behaviour to indeed something in xsltproc (as James suspected) or libxslt, and then to between[1] versions 1.1.34 and 1.1.35 of the latter. >From there, a commit to add test coverage[2] looked relevant, and sure enough, the referenced commit[3] in libxml2 linked to a report[4] exhibiting this same problem. [1] - https://gitlab.gnome.org/GNOME/libxslt/-/compare/v1.1.34...v1.1.35 [2] - https://gitlab.gnome.org/GNOME/libxslt/-/commit/ea1c27fca299f4f29d8bd1e29ac2ad21aea81bcc [3] - https://gitlab.gnome.org/520zym/libxml2/-/commit/9f42f6baaa91b6461ddfce345c174ea5f1ee73c3 [4] - https://gitlab.gnome.org/GNOME/libxslt/-/issues/37
