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.

zeitgeist 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 tried to use diffoscope to check that they make no difference to the
built binaries (as is usually the case for similar changes), but in a
rebuild with these patches applied, lots of offsets in the shared
library seem to be different. As far as I can see, the actual code is
the same. Perhaps this package isn't 100% reproducible or deterministic?

Thanks,
     smcv