https://buildd.debian.org/status/fetch.php?pkg=librsvg&arch=amd64&ver=2.57.92%2Bdfsg-1&stamp=1710036934&raw=0

test tests::svg2_gradient_01_b_svg ... ok

failures:
---- tests::rtl_tspan_svg stdout ----
rtl-tspan: 2655 pixels changed with maximum difference of 112
out: /<<PKGBUILDDIR>>/tests/output/rtl-tspan-out.png
diff: /<<PKGBUILDDIR>>/tests/output/rtl-tspan-diff.png
thread 'tests::rtl_tspan_svg' panicked at 'surfaces are too different', rsvg/src/test_utils/reference_utils.rs:85:25
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    tests::rtl_tspan_svg

test result: FAILED. 744 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.76s

error: test failed, to rerun pass `-p librsvg --test reference`
make[5]: *** [Makefile:1610: check-local] Error 101

Cheers
-- 
Sebastian Ramacher

This appears to have been caused by upgrading pango1.0 from 1.52.0
to 1.52.1. The librsvg test suite is unfortunately very sensitive to
differences in the exact version of dependencies like pango1.0.

Please can we minimize disruptive changes in unstable until the ongoing
time_t disaster is resolved? In most cases, experimental is available
for testing newer upstream releases.

(For example glib2.0 2.80.x is only in experimental despite being an
upstream stable release, and I think that was an appropriate decision
at this stage.)

Thanks,
    smcv

Control: tags -1 + pending

For now, I'm testing an upload that will temporarily disable this test,
after which this bug can be downgraded to non-RC.

After pango1.0 >= 1.52.1 reaches testing, we should add a versioned
build-dependency on it and re-enable this test, updating the reference
rendering if necessary (see also the upstream bug report
https://gitlab.gnome.org/GNOME/librsvg/-/issues/1063).

    smcv

Control: retitle -1 librsvg: reftest regression for rtl-tspan with pango1.0 1.52.1: 2655 pixels differ from reference
Control: severity -1 important

Uploaded, downgrading severity accordingly.

    smcv