As announced in
https://lists.debian.org/debian-devel/2025/08/msg00150.html I would like
to try to remove libgirepository1.0-dev during the forky cycle, but we
cannot do this while it has reverse-dependencies. I still plan to do a
mass-bug-filing for this, but for the moment I have only been fixing
GNOME and GNOME-adjacent packages, and a few of the highest-visibility
packages in other teams.

Mass-filed bugs will be usertagged to appear at the link above, and
marked as blockers for this bug.

For more information about the changes needed in dependent packages,
please see
https://salsa.debian.org/gnome-team/gobject-introspection/-/blob/debian/latest/debian/libgirepository1.0-dev.README.Debian?ref_type=heads
which will be kept up-to-date with any changes to the advice given. A
version of this file (possibly outdated) is included in the
libgirepository1.0-dev package.

    smcv

https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers@lists.alioth.debian.org&tag=libgirepository1.0-dev
based on information from dak:
https://people.debian.org/~smcv/temp/2025/mbf-libgirepository1.0-dev/

but _rene_ points out that this missed at least libreoffice, which has a
Build-Depends-Arch on libgirepository1.0-dev.

This might mean that 'dak rm -R -n -b libgirepository1.0-dev' doesn't
know about Build-Depends-Arch, which if true seems concerning, since
that's the same tool the ftp team use to see whether it's safe to remove
packages? (Or perhaps I'm just using it wrong.)

     smcv