Bug#1049413: update to 2.56
On 16.09.23 23:32, Jeremy Bícha wrote: On Sat, Sep 16, 2023 at 5:26 PM Matthias Geiger wrote: I would suggest to switch the upstream to the source on crates.io and provide the "crate data" on top. Are you able to provide the "crate data" on top of the current librsvg in Unstable? Could you try patching glycin-loaders to accept librsvg 2.54? I see in the git log that the dependency appears to have been arbitrarily set from 2.57 to 2.56 and then back to 2.57 so maybe the dependency is stricter than it needs to be. Thank you, Jeremy Bícha a quick wget of the crate tarball shows the "crate data" is the raw source code under src/ , tests/ and benches plus example.svg, build.rs and Cargo.toml. I'll test tomorrow if that installed under /usr/share/cargo/registry will work for a build. best, -- Matthias Geiger (werdahias) Debian Maintainer "Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1049413: update to 2.56
On Sat, Sep 16, 2023 at 5:26 PM Matthias Geiger wrote: > I would suggest to switch the upstream to the source on crates.io and > provide the "crate data" on top. Are you able to provide the "crate data" on top of the current librsvg in Unstable? Could you try patching glycin-loaders to accept librsvg 2.54? I see in the git log that the dependency appears to have been arbitrarily set from 2.57 to 2.56 and then back to 2.57 so maybe the dependency is stricter than it needs to be. Thank you, Jeremy Bícha
Bug#1049413: update to 2.56
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 OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
