As announced in [MBF] and [#1117130] the GNOME team would like to remove
libgirepository1.0-dev during the forky cycle. According to dak, this
source package contains a Depends or Build-Depends on
libgirepository1.0-dev which blocks its removal.

The README.Debian for libgirepository1.0-dev [README] provides advice on
how to choose an appropriate replacement for libgirepository1.0-dev, and
will be updated if new information becomes available.

sugar-toolkit-gtk3 seems to follow the typical pattern for a package that has a
public C/C++ library with GObject-Introspection bindings, so it can
probably follow the same conversion steps as other libraries like
libmanette:
<https://salsa.debian.org/gnome-team/libmanette/-/merge_requests/6>.

References:
[README]:
https://salsa.debian.org/gnome-team/gobject-introspection/-/blob/HEAD/debian/libgirepository1.0-dev.README.Debian
    file:///usr/share/doc/libgirepository1.0-dev/README.Debian.gz
[#1117130]:
https://bugs.debian.org/1117130
[MBF]:
https://lists.debian.org/debian-devel/2025/08/msg00150.html

Thanks,
    smcv

Control: tags -1 + patch

Please consider the attached patches.

I've confirmed using diffoscope that the only change to the contents of
the binary packages is the addition of missing Depends/Provides in the
-dev package:

│ │ │ │  Package: libsugarext-dev
│ │ │ │  ...
│ │ │ │ -Depends: gir1.2-sugarext-1.0 (= 0.121-1), libsugarext0 (= 0.121-1), libasound2-dev, libglib2.0-dev, libgtk-3-dev, libice-dev, libsm-dev, libx11-dev, libxfixes-dev, libxi-dev
│ │ │ │ +Depends: libsugarext0 (= 0.121-1), libasound2-dev, libglib2.0-dev, libgtk-3-dev, libice-dev, libsm-dev, libx11-dev, libxfixes-dev, libxi-dev, gir1.2-gdk-3.0-dev, gir1.2-gtk-3.0-dev, gir1.2-sugarext-1.0 (= 0.121-1)
│ │ │ │ +Provides: gir1.2-sugarext-1.0-dev (= 0.121-1), gir1.2-sugargestures-1.0-dev (= 0.121-1)

piuparts also passes. Not tested beyond that.

Thanks,
     smcv