Those are not public symbols, they are part of the implementation-specific layer of librsvg (all symbols named "rsvg_rust_*" fall in this category).
Neither the C headers nor the GObject introspection and Vala vapi files installed by librsvg2-dev expose them. The symbols are exported in the so file though, so there is a very slim chance that they might be used in the wild. However according to http://codesearch.debian.net/ they are not used in Debian, and Google doesn't return any meaningful reference in third-party code either, so this looks quite safe to me.
Hey Łukasz, that's a good point.
Those are not public symbols, they are part of the implementation- specific layer of librsvg (all symbols named "rsvg_rust_*" fall in this category).
Neither the C headers nor the GObject introspection and Vala vapi files installed by librsvg2-dev expose them. The symbols are exported in the so file though, so there is a very slim chance that they might be used in the wild. However according to http:// codesearch. debian. net/ they are not used in Debian, and Google doesn't return any meaningful reference in third-party code either, so this looks quite safe to me.
This is not the first time something like this happens in the librsvg Debian package without a soname bump, FWIW: https:/ /salsa. debian. org/gnome- team/librsvg/ -/commit/ 8c692609c3bba7d 70bb269082a2e3b 16f2f19007.