The `image` crate's AVIF decoding feature is named `avif-native`. `avif`
is the encoding feature.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

We didn't have one; that's why we didn't notice the incorrect name for
the cargo feature that the image crate uses for decoding AVIF.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

I forgot about SRGB correction.  Or something.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Per https://github.com/image-rs/image-png/pull/400, updating the png
crate for the new bitflags would cause a breaking change.  Looks like
the maintainers want to wait.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

Duplicates pointed out by cargo-deny

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

This started failing in the msys2-mingw64 job.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1003>

cargo: Fix embedded AVIF images

See merge request GNOME/librsvg!1003

marge-bot has had GNOME wide Developer access for a while, which should be sufficient.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1004>

doap: Remove marge-bot maintainer entry

See merge request GNOME/librsvg!1004

This kwarg was added in 1.5.0, but we require 1.2.0. Anyway, an
explicit error message is much clearer to the user.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1006>

Change all references to ./gir/generator.py and add a note about
running git submodule update.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1006>

Fix compat with meson <1.5 and remove the need for a broken symlink

See merge request GNOME/librsvg!1006

Fuzz testing found that the cssparser-color crate's hsl_to_rgb()
asserts that it is handed values in [0.0, 1.0].

Fixes https://gitlab.gnome.org/GNOME/librsvg/-/issues/1117

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1007>

The baseFrequency gets multiplied by the pixel coordinate within tile
size to obtain the base value for computing that pixel's noise
function.  Avoid integer overflow by limiting the maximum
baseFrequency to a reasonable value (currently 32768, which is
pixman's maximum image size).

Fixes https://gitlab.gnome.org/GNOME/librsvg/-/issues/1115

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1007>

Two fixes from fuzz testing

Closes #1115 and #1117

See merge request GNOME/librsvg!1007

Fixes https://gitlab.gnome.org/GNOME/librsvg/-/issues/1107

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1008>

https://bugzilla.gnome.org/show_bug.cgi?id=749415 was caused by
incorrect and duplicated logic to decide when to create a temporary
surface for a stacking context (... back when we didn't even have the
concept of a stacking context).

The test is a chunk of a diagram with a bunch of text elements with
very particular transforms.  Any minute change in the text rendering
stack tends to change the rendering slightly.

This is not a useful test anymore; we already have other tests for
text with transforms.

For reference, the commit that originally introduced the tests is
cb7fd6b6

Fixes https://gitlab.gnome.org/GNOME/librsvg/-/issues/1102

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1009>

(#1102): Remove obsolete test for Bugzilla bug 749415

Closes #1102

See merge request GNOME/librsvg!1009

(#1107): Roll back the MSRV to 1.77.2 for Windows/MSVC builds

Closes #1107

See merge request GNOME/librsvg!1008

Fixes #1120

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1011>

meson: Run -Wl,--version-script detection with a configure generated file

Closes #1120

See merge request GNOME/librsvg!1011

Rationale of this: https://gitlab.gnome.org/GNOME/librsvg/-/issues/1107,
so that we force using Rust 1.77.2 for our builds

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1012>

CI: Force Rust 1.77.2 for Visual Studio builds

See merge request GNOME/librsvg!1012

See:
https://sourceware.org/git/?p=binutils-gdb.git;h=aa02037b08312eece5c06e1e98b2ce8b30993c5c

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1013>

meson: Ensure compatibility with Binutils < 2.39

See merge request GNOME/librsvg!1013

In case the install prefix and the gdk-pixbuf prefix are different (which
is the default in MSYS2 packaging for example) we need to override the
prefix defined in the .pc file with the one we are installing to.

This fixes the loader being installed into the wrong directory under MSYS2.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1015>

Mingw cargo builds "pixbufloader_svg.dll" without any prefix.
This fixes a meson install error where it can't find the DLL due to
the name not matching.

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1015>

meson: mingw build fixes

See merge request GNOME/librsvg!1015

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1016>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1016>

Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/1016>

Prepare 2.58.94

See merge request GNOME/librsvg!1016