Your message dated Fri, 31 Oct 2025 18:49:43 +0000
with message-id <[email protected]>
and subject line Bug#1118895: fixed in lua-lgi 0.9.2-6
has caused the Debian Bug report #1118895,
regarding lua-lgi: depends on non-multiarch-friendly libgirepository1.0-dev
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.)
--
1118895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118895
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lua-lgi
Severity: normal
Tags: forky sid
User: [email protected]
Usertags: libgirepository1.0-dev
Control: block 1117130 by -1
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.
lua-lgi seems to be a language binding that uses libgirepository-1.0,
so probably it should use libgirepository-1.0-dev (or
libgirepository-2.0-dev) as its replacement.
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
--- End Message ---
--- Begin Message ---
Source: lua-lgi
Source-Version: 0.9.2-6
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lua-lgi, 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.
Bastian Germann <[email protected]> (supplier of updated lua-lgi 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: Fri, 31 Oct 2025 18:53:49 +0100
Source: lua-lgi
Architecture: source
Version: 0.9.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1118895
Changes:
lua-lgi (0.9.2-6) unstable; urgency=medium
.
* Team upload
* girepository: Apply restructuring (Closes: #1118895)
Checksums-Sha1:
2fa73c37602af5e92dc7574ec9a90529d1847783 2022 lua-lgi_0.9.2-6.dsc
83d4c6cad35dcb3dfcb4d1bc7e7098bf93d3048d 7268 lua-lgi_0.9.2-6.debian.tar.xz
8e9870b02dce44a2613ec1977246d1fcf5a4b5c6 13208 lua-lgi_0.9.2-6_source.buildinfo
Checksums-Sha256:
c956c9f884eaeaabcf06e1199bf31a426a21b1d07d72236d4a3a1cf325fefc05 2022
lua-lgi_0.9.2-6.dsc
f37a4f47b3a9c603050173308ce751cc5f5a7232fcefc866f813d5ad82d0cc7d 7268
lua-lgi_0.9.2-6.debian.tar.xz
aaaf300d775bc79b1bd91882d4bd5359506b6edf53f33e5911081d25be979240 13208
lua-lgi_0.9.2-6_source.buildinfo
Files:
af6ff5e9ace71fb49dddd7c03167cac6 2022 interpreters optional lua-lgi_0.9.2-6.dsc
68de9954e0176a9d2172a118da441f09 7268 interpreters optional
lua-lgi_0.9.2-6.debian.tar.xz
744655592761103005cb9e0e4cdd81e0 13208 interpreters optional
lua-lgi_0.9.2-6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmkFAIIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFLrQDACOqIkS5xPLl0Dnfd1g3tvEanfJ9BXFtLAi
jISw0KIWrZ0fXk0DcfSbg7ATLBuOzTWfnEWOZ7jXa2XF9Adjf/QCRIu9ngMzD2Qp
Eq+gquImNVELatlo33Su/gXVnHbUyfVnmffCe67B9w7pQ+vJxhu+Odz8kezm2Ta2
69/w9AmqpB7nXnKRBPYveGvuPVkLTiF7h2pbeKjRZpiyy19rOqmawpKVh41b4jbC
KFhyJQh7CNQjl85Vz9u87bVJbtx/lWvWoXhcdfRgUocA1Xs2oWEWYgCVziZCFMWK
jiWsmWw0yvtj2K++BwD4S2vabRkebQhArrV9PPBcnJQEl0Xlmzd9j1UJe7d4d/9t
eaMJJo1nWET9sJAXHAobGGsg2pk77+uuveaZ/TTtulFK9/R31zolVuhjaxIYu+bn
w1cEw9O1vwZe7QScjWcSbqpB3CKVB1IbgUsoXUvpNOj33LJU1oltO20DFahTnhmp
k4reguuAk9japch5LxTgxnzz2uV8lf0=
=juA1
-----END PGP SIGNATURE-----
pgpOxn9zVHEzC.pgp
Description: PGP signature
--- End Message ---
