Your message dated Thu, 16 Jul 2026 13:18:47 +0000
with message-id <[email protected]>
and subject line Bug#1140049: fixed in libayatana-common 0.9.13-1
has caused the Debian Bug report #1140049,
regarding gir1.2-ayatanacommon-0.1: typelibs installed in incorrect directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1140049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140049
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gir1.2-ayatanacommon-0.1
Version: 0.9.12-1
Severity: grave
Tags: upstream
Justification: renders package unusable

A smoke-test similar to this one should work for every package 
containing "public" typelibs:

$ podman run --rm -it debian:sid-slim
# apt update
# apt upgrade
# apt install python3-gi gir1.2-ayatanacommon-0.1
# python3
>>> import gi
>>> gi.require_version('ayatanacommon', '0.1')
>>> from gi.repository import ayatanacommon
>>> assert ayatanacommon.utils_is_gnome() in (True, False)

But for gir1.2-ayatanacommon-0.1, it currently fails:

>>> gi.require_version('ayatanacommon', '0.1')
Traceback (most recent call last):
  File "<python-input-2>", line 1, in <module>
    gi.require_version('ayatanacommon', '0.1')
    ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 150, in 
require_version
    raise ValueError(f"Namespace {namespace} not available")
ValueError: Namespace ayatanacommon not available

because the typelib is installed to a directory that is not searched by 
GObject-Introspection: /usr/lib/x86_64-linux-gnu/girepository-1.2/ 
instead of the correct /usr/lib/x86_64-linux-gnu/girepository-1.0/.

Similarly the -dev package installs the GIR XML into /usr/share/gir-1.2/ 
instead of the correct /usr/share/gir-1.0/. I know the XML says 
"<repository version="1.2"..." but the correct directory names still 
have 1.0 in them, as documented in 
file:///usr/share/doc/gobject-introspection/policy.txt.gz:

> Note that the format is specified in the .gir file
> itself and may not match the /usr/lib/*/girepository-1.0 and
> /usr/share/gir-1.0 paths.

This appears to have been an intentional upstream change:

>   * debian/:
>     + Upstream installs gir1.2 files now to gir-1.2 directory.

which surprises me, because I don't see how this change can have worked 
successfully. How was it tested?

It is often a good idea for packages with GObject-Introspection to have 
a superficial autopkgtest similar to 
<https://salsa.debian.org/gnome-team/libadwaita/-/blob/debian/latest/debian/tests/python-gi-test?ref_type=heads>
to confirm that the intended typelib API can be loaded successfully.

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: libayatana-common
Source-Version: 0.9.13-1
Done: Mike Gabriel <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libayatana-common, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel <[email protected]> (supplier of updated libayatana-common 
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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 16 Jul 2026 14:42:41 +0200
Source: libayatana-common
Architecture: source
Version: 0.9.13-1
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers <[email protected]>
Changed-By: Mike Gabriel <[email protected]>
Closes: 1140049
Changes:
 libayatana-common (0.9.13-1) unstable; urgency=medium
 .
   * New upstream release.
     -  Resolves wrong installation path of GIR files. (Closes: #1140049).
   * debian/*.install:
     + Adjust GIR installation paths back to gir(|epositury)-1.0.
   * debian/tests/:
     + Add python-gi-test. Thanks to Simon McVittie for providing a template
       for this.
Checksums-Sha1:
 073e4d6c08612fbe7405cc3faf0c8091dd53dbaf 2965 libayatana-common_0.9.13-1.dsc
 1e70933f1a1763f2e080781c11b72ff522590c92 45894 
libayatana-common_0.9.13.orig.tar.gz
 235be01a980cc45869ae1d46fa473a6a11c25cfb 833 
libayatana-common_0.9.13.orig.tar.gz.asc
 639d8511253180ab9088bcc8d37ad06ce830b84f 14260 
libayatana-common_0.9.13-1.debian.tar.xz
 5477a8bdb5a2d5a90af500a0d5e1bf4df6afd6d6 18601 
libayatana-common_0.9.13-1_source.buildinfo
Checksums-Sha256:
 c08091fd76101f68e8a62bbe7141caa813a50b46393ced32ce26e2cd89e48342 2965 
libayatana-common_0.9.13-1.dsc
 e9ab2ee553703314bf0feb956cdd579fa99130ac821c4410c5bc4b05649995b3 45894 
libayatana-common_0.9.13.orig.tar.gz
 1f0676e1d6de61bc05c6c36b923ae5a2df1d92d0b805a3312ac1e02b062bdcdb 833 
libayatana-common_0.9.13.orig.tar.gz.asc
 c1502a34ef99fd05bed178e3d6f36e10179832ed7e98fd48ccfa0dd8e5e999e8 14260 
libayatana-common_0.9.13-1.debian.tar.xz
 79a35a1637e99316ec3c3940b8ce80b49c7dbeff0bfea8df2414e4b81200bfc8 18601 
libayatana-common_0.9.13-1_source.buildinfo
Files:
 a375e9f4a903c82dcf3cb826ee72ae9e 2965 libs optional 
libayatana-common_0.9.13-1.dsc
 cbafbf8240c362f77ce0d69dcc8849d6 45894 libs optional 
libayatana-common_0.9.13.orig.tar.gz
 0dd2a8ffee25699cf09d97eeda5f659c 833 libs optional 
libayatana-common_0.9.13.orig.tar.gz.asc
 d0bc843f1157404ef88c805378d4a625 14260 libs optional 
libayatana-common_0.9.13-1.debian.tar.xz
 01d5612a76b558fb80970ab08640effd 18601 libs optional 
libayatana-common_0.9.13-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCgAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmpY1egVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxXykP/2Cbxd5N1240tNKm+MO/7YO2Qtwf
1woi3gExskLjoZPRpB2fUiGi83rAfQzTLXckQ2AZhAIiYQiBc6QSYkHsETeFbcui
Zux31IDdoJZc5JhfIQffkUs1mzqzD4HDukD4j4ltBUuhOdwdrL3X3P3OrSFvNx9a
L+bgK9/1lYO0iN3mnuCGm5ZMZEZE3x8JVbYB8vnzQn9hPMtT4t6tHryMFHzcPgvE
WXiXepZqzJxoPu09BY1XRaLUwZFK8JsXsOt4NxGNaSrp+nqDlFOV6XeGOimdKyfG
9g65wkt6upPxpDWm+Y/CLrLq06WZcwD7BgJpI8wxfTtnW5ybp9Jbmzu1alCf+4Xy
tSYSNX5LJsC736CjjdyoC0p5cIfzzrqb4sSUUZsXtEgxr67CHcvCKiHSi2R8TXYm
sRET2AzAvYwupsDWoxnejfZr8KHvtjwTiY2vyePVTQcQDxJrkvQzU8MQhOKZKDuw
f7/DHAOqgpq/fWEi3jos41r4XuHkAmaIpF0N+sYStsuTKqglQtgx7PNELPWAwT+m
0TM9o69n2/w0JVYaC+nY3BYdSPeI70coE7aiIcGtQ2PJ7QD+AR2L+wYaDyAjSl27
FZU6NRhUwwqJqKLbvcquAKoWcss6iNr49T6FfXyU1P6XRRCxGLnYYYGPnuEMWmAM
0fsMA8zzBhy7kWjx
=S4Tm
-----END PGP SIGNATURE-----

Attachment: pgpLMTmnvP9oP.pgp
Description: PGP signature


--- End Message ---

Reply via email to