Since June 2024 librsvg has been updated to 2.50 (see T265549#9867973)
Several librsvg issues are still not fixed in 2.50 (Debian Bullseye), but are in later versions.
Debian Bookworm (stable) ships a more recent version: 2.54 (as of December 2024)
An alternative to update might be switching to a different (less buggy) renderer, see T40010
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | BUG REPORT | None | T370044 PNG thumbnail of SVG file: Text not centered and cut off | ||
| Resolved | TheDJ | T381674 Update librsvg to version ≥ 2.54 | |||
| Resolved | hnowlan | T355020 Upgrade Thumbor to Debian Bookworm | |||
| Resolved | hnowlan | T336881 [XL] Upgrade Thumbor to bullseye | |||
| Resolved | AntiCompositeNumber | T260285 Use ImageMagick for XCF rendering instead of xcftools |
Thumbor is currently running with a bookworm image (T355020):
runuser@thumbor-main-76fcf686cf-w2kxb:/srv/service$ cat /etc/debian_version 12.8 runuser@thumbor-main-76fcf686cf-w2kxb:/srv/service$ rsvg-convert --version rsvg-convert version 2.54.7
@hnowlan : Do I understand you correctly that all svgs on Wikimedia-Commons are currently rendered by librsvg-2.54.7 ? So this task can be closed as completed (Status: Resolved)?
I created this task, since a specific bug (T370044#10040737) is partially fixed in 2.57, but is not currently working on Wikimedia. and I limted updateing to 2.54 since it is the version of Debian bookworm.
Debian Trixie (currently testing) will ships librsvg 2.59, which should (partually) fix this bug.
I assume updating to librsvg 2.59 will wait for updating Thumbor to Debian Trixie, which is stalled at least till it is stable released, and listed on https://wikitech.wikimedia.org/wiki/Operating_system_upgrade_policy ?
Does this change need to be announced in Tech News? I see some back-and-forth in the task above (removing and re-adding the User-notice tag - @Pppery). If it does need to be announced, please could someone propose some wording, of what editors will want/need to learn about this change? Thanks!
If this was truly done in July then there's no point in announcing it in December, so removing the tag.
(The announcement I was trying to produce with T381674#10388762 would have been similar in wording to T265549#9868598, but we've totally missed our chance to announce it. I had interpreted T381674#10387052 as cleanup from the "create subtask" interface copying project tags, not an independent claim it doesn't need announcing)