- Package:
- libatspi2.0-dev
- Source:
- libatspi2.0-dev
- Description:
- Development files for the assistive technology service provider
- Submitter:
- Christian Klein
- Date:
- 2024-03-03 01:36:03 UTC
- Severity:
- normal
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 This breaks libgtk-3-dev multiarch install, since libgtk-3-dev depends on libatspi2.0-dev via libatk-bridge2.0-dev. Looking at the changelog, I don't see why the additional dependency is necessary. 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.
Hello, Christian Klein, le sam. 02 mars 2024 16:33:15 +0100, a ecrit: 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. Samuel
Control: clone -1 -2
Control: reassign -2 gobject-introspection 1.78.1-15
Control: retitle -2 dh_girepository: generates unwanted dependency on libgirepository1.0-dev if that package is installed
Control: severity -2 important
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 and will try to fix the bug in dh_girepository
soon. I know that regressions are unacceptable, but this week there have
been several unrelated time-sensitive issues for which I have been made
a single point of failure, so I hope you will forgive me for not putting
this right at the top of my queue.
The bug is that if libgirepository1.0-dev is installed, dh_girepository
will wrongly generate dependencies on that package in preference to
gir1.2-glib-2.0-dev. This is because, for backwards compatibility
with packages that have not yet been updated to look for GIR XML
in a multiarch-friendly location, libgirepository1.0-dev provides a
symbolic link to the architecture-specific GIR XML for GLib-2.0 in a
non-multiarch-friendly location. This backwards compatibility glue is also
the reason why libgirepository1.0-dev cannot be Multi-Arch: same.
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:
diff --git a/debian/control b/debian/control
index 5408552..1dd2830 100644
--- a/debian/control
+++ b/debian/control
@@ -11,8 +11,10 @@ Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13),
libx11-dev, libxtst-dev,
meson (>= 0.63.0),
pkgconf,
- libgirepository1.0-dev,
gtk-doc-tools, gi-docgen, python3-sphinx,
+ gir1.2-dbus-1.0-dev,
+ gir1.2-glib-2.0-dev,
+ gir1.2-gobject-2.0-dev,
gobject-introspection | dh-sequence-gir,
xauth <!nocheck>,
xvfb <!nocheck>,
(Compile-tested only, I have not attempted to verify that the resulting
binaries are perfect; at the moment I'm only looking at this while I wait
for an urgent glib2.0 bug fix to finish running automated tests, and I
will have to re-prioritize back to glib2.0 as soon as it is ready. I
apologise for not providing an exhaustively-tested, production-ready
solution right now.)
smcv
Hello, Simon McVittie, le dim. 03 mars 2024 00:43:12 +0000, a ecrit: Heh :) No problem, thanks for the quick feedback! Oh, indeed. This does look right and produces correct binaries, I'll upload that, thanks! Samuel
We believe that the bug you reported is fixed in the latest version of
at-spi2-core, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065316@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Thibault <sthibault@debian.org> (supplier of updated at-spi2-core package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 03 Mar 2024 02:19:20 +0100
Source: at-spi2-core
Architecture: source
Version: 2.51.90-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team <pkg-a11y-devel@alioth-lists.debian.net>
Changed-By: Samuel Thibault <sthibault@debian.org>
Closes: 1065316
Changes:
at-spi2-core (2.51.90-2) unstable; urgency=medium
.
* control: Replace libgirepository1.0-dev build-dep with gir1.2-dbus-1.0-dev
gir1.2-glib-2.0-dev gir1.2-gobject-2.0-dev. Closes: Bug#1065316.
Checksums-Sha1:
08294debdf06eba7e8a7e2d0cf6ed57075440f3c 3781 at-spi2-core_2.51.90-2.dsc
bd4c776fc262b140fa411ab7a722136d9fc29d31 31836 at-spi2-core_2.51.90-2.debian.tar.xz
0aab974e4d8c1d1b544811460ed1945bd5827245 19021 at-spi2-core_2.51.90-2_amd64.buildinfo
Checksums-Sha256:
d3e1dd24e5e7405038668633970a9219b26d2b15cb3844d5ddcfc5e7836da362 3781 at-spi2-core_2.51.90-2.dsc
88d1e753bc8b964d33b2008f436dba96aed9dfe32ef0d4bb614f4079751f5819 31836 at-spi2-core_2.51.90-2.debian.tar.xz
971a73f5ae873bee97e1d44e25c243333557e9b06fa65d099861c5c966b0d89e 19021 at-spi2-core_2.51.90-2_amd64.buildinfo
Files:
25fdf68fdf8f0e390cbab8e93cbe3dba 3781 misc optional at-spi2-core_2.51.90-2.dsc
54cec93093d34f61c46a3c23c82395eb 31836 misc optional at-spi2-core_2.51.90-2.debian.tar.xz
fdf55d1fc0da61982189361d28490eaf 19021 misc optional at-spi2-core_2.51.90-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmXj0JsACgkQ5pG0tXV4
H2LNKA/+JedbbUEGHsfia6FPPnbDbjvCcj5qUZ0wb9a2T3wR1Z+9EAuTVw7RB33T
ylXJGHnxkSBrpzAifSHES94Sajfra+MSQQT6OeZnzN7/9MGKBGUdwXd3q75wVpGr
kfS2Mn8ddw5n7VuBpDFz7wLs9y/7LykEwu/VTgjE0Oq+K4bX2fV9Ph7myczcqfUd
i9PtEyv5VXQYmke55v/cYOLxZxCgsxdsgfdmgqqekrlw5iw3JM40VWrX3WBPgztx
9JbYU49/xBB6gMB+LIFQpUWtwRC9LhEkhqGcrCYUMT+aGdfa64kBgWZMpmDEJy2z
ST3c8P75wOP710QRVrm9vzEjPrXY9T5TQvvn10S4e5+UlGh9IfTkFAWCQjTfVHz+
Euc7Efu6B255ev5iEfoN0RnsyO60+wFgk4zVMVchFocLkyT2PHsiTIeQBny6Hgxr
ljvtAJSBEeV8OIOugjk8NRdBIa4p3kMRgi4PCAlG38TYwLu1oucZTgCLBBbQXI+j
2za0kz/xhS/MEUVGTZ62GoKZGkuYK5+OT5ZdK4lE+Kyhz6iiyKl3CkKjRz6EGHDu
7DqhzX5Rj4WctF8elamISP29mvfQyQK28/os1ng8XX5tP/9RhrntS//M7MOWbnOX
pihxL+is7dKEUSZuorbwO7G0GvhDbg4YCKgevuQ64hKhkPI+hJA=
=kc72
-----END PGP SIGNATURE-----