Bug#1049413: update to 2.56

[Matthias Geiger]

Upstream also chose to publish librsvg on crates.io [0].

This is a bit of an issue since src:librsvg in debian does not provide 
the librsvg crate. Other GNOME apps [1] started depending on the crate 
version,

which results in a build failure as the crate data is not found (this 
affects glycin-loaders and by extension loupe right now).

I could disable svg support, but since this is a common image format 
this doesn't look like a good option to me.

I would suggest to switch the upstream to the source on crates.io and 
provide the "crate data" on top.

Otherwise please find a way to provide this source code as it'll be 
needed inevitably at some point. I can package all remaining 
dependencies to fully de-vendor librsvg.

Another option would be that the rust source code for librsvg is 
provided by a src:rust-librsvg package maintained by the Rust 
maintainers (not building anything else).

Let me know what you think.

[0] https://crates.io/crates/librsvg

[1] 
https://gitlab.gnome.org/sophie-h/glycin/-/blob/main/loaders/glycin-svg/Cargo.toml?ref_type=heads#L14


-- 
Matthias Geiger (werdahias)
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x18BD106B3B6C5475.asc
Type: application/pgp-keys
Size: 4036 bytes
Desc: OpenPGP public key
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20230916/5d740c76/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20230916/5d740c76/attachment.sig>