On Fri, 14 Mar 2025 at 17:08:19 -0400, Jeremy Bícha wrote:
I'm thinking about closing this bug since the real bug is
https://bugs.debian.org/1100054 and practically we're going to fix
things there rather than change gobject-introspection.
This issue isn't causing practical problems for users of Debian, it's
just preventing building a bunch of Rust packages using
gir-rust-code-generator once an intermediate package (like glib2.0
already in Testing or libadwaita-1 migrating to Testing now) is built
with gobject-introspection >= 1.83.
I think that's reasonable. It's unfortunate that g-i added a feature
that broke the build of bindings generators that depend on it, but
realistically they are not going to revert it now, and realistically
we're not going to roll back to 1.83.x+really1.82.x in unstable either,
so the only way is forward (making gir-rust-code-generator understand
the new element and either make use of it, or if that's too difficult,
accept and ignore it for now like GLib does).
smcv
