libatspi2.0-dev is no longer muti-arch installable.
It now has a dependency on libgirepository1.0-dev, which isn't multi-arch. 2.50.0-1 didn't have that dependency
Looking at the changelog, I don't see why the additional dependency is necessary.
This breaks libgtk-3-dev multiarch install, since libgtk-3-dev depends on libatspi2.0-dev via libatk-bridge2.0-dev.
Even worse, for i386, this now pulls in ~250MB additional packages, because libgirepository1.0-dev needs gobject-introspection:i386, which pulls in gcc-i686-linux-gnu.
Christian Klein, le sam. 02 mars 2024 16:33:15 +0100, a ecrit:
libatspi2.0-dev is no longer muti-arch installable.
It now has a dependency on libgirepository1.0-dev, which isn't multi-arch. 2.50.0-1 didn't have that dependency
Looking at the changelog, I don't see why the additional dependency is necessary.
This is coming from gir:Depends:
./debian/libatspi2.0-dev.substvars:gir:Depends=gir1.2-atspi-2.0 (= 2.51.90-1), gir1.2-dbus-1.0-dev, gir1.2-gobject-2.0-dev, libgirepository1.0-dev
I don't know the ins and outs why this comes like this, thus asking for
help on this.
This was an unintended regression caused by changes made in gobject-introspection, ironically to make multiarch co-installability and cross-compilation of GObject-Introspection data possible.
I am sorry to have inconvenienced you
Samuel or other AT-SPI maintainers, if you want to avoid this unwanted dependency while also bringing libatspi2.0-dev one step closer to being cross-compilable itself, please consider replacing the build-dependency on libgirepository1.0-dev with the canonicalized package names corresponding
to the GIR modules required by the upstream source, which according to
the build log means this:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 07:22:15 |
Calls: | 6,706 |
Files: | 12,236 |
Messages: | 5,350,636 |