Your message dated Sat, 04 May 2024 16:50:02 +0000 with message-id <e1s3iai-00fvef...@fasolo.debian.org> and subject line Bug#1066900: fixed in gobject-introspection 1.80.1-2 has caused the Debian Bug report #1066900, regarding g-ir-compiler: generates incorrect typelib when cross-compiling with different type sizes 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 ow...@bugs.debian.org immediately.) -- 1066900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: gobject-introspection Version: 1.78.1-16 Severity: serious Justification: results in misbuilt packages X-Debbugs-Cc: debian-cr...@lists.debian.org When it converts GIR XML to binary typelib files, g-ir-compiler replaces abstract types such as int and gsize (size_t) with concrete types such as gint32 (int32_t) and guint64 (uint32_t). The way in which it does this depends on the type sizes discovered at configure time when compiling g-ir-compiler. This means that cross-compiling for an arm64 or riscv64 host on an amd64 build machine should be OK, but cross-compiling for armhf or i386 on amd64 will produce invalid typelibs. I am sorry that I didn't notice this sooner. A crude solution to this would be to revert gobject-introspection and gobject-introspection-bin to be Multi-Arch: no, so that building typelibs is no longer possible in cross-builds. [1] A more refined version of that would be to change the relationship between gobject-introspection and gobject-introspection-bin so that instead of the current arrangement where the dependency is on a virtual package gobject-introspection-linux-little-endian, it would be on a virtual package that also reflects the word size in use: gobject-introspection-linux-lp64-little-endian or similar. This would preserve the ability to cross-compile in only those situations where it would be correct. [2] A workaround to enable cross-compiling between word sizes would be to use the host architecture g-ir-compiler, and run it via qemu-user. Unfortunately this will greatly increase the amount of host-architecture code that needs to be run via emulation. In the short term, I'm going to do [1] or [2] as a matter of urgency, to ensure that Ubuntu 24.04 doesn't ship with faulty cross-tools that claim to work but actually do not. Any further improvement can be in-scope for #1030223 "gobject-introspection: make cross-compilation possible". If we do [2] then we will have to be extra-careful to distinguish between dissimilar ILP32 ABIs, because gobject-introspection currently hard-codes that it thinks time_t is long and off_t is size_t, both of which happen to be correct on LP64 and on i386, but neither of which is correct on an ILP32 architecture that has transitioned to large file support and 64-bit time_t (such as armel and armhf in 2024) or an ILP32 architecture that always had 64-bit off_t and time_t (such as x32). I apologise for having been insufficiently careful when enabling this feature. smcv
--- End Message ---
--- Begin Message ---Source: gobject-introspection Source-Version: 1.80.1-2 Done: Jeremy Bícha <jbi...@ubuntu.com> We believe that the bug you reported is fixed in the latest version of gobject-introspection, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha <jbi...@ubuntu.com> (supplier of updated gobject-introspection 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 04 May 2024 12:39:14 -0400 Source: gobject-introspection Built-For-Profiles: noudeb Architecture: source Version: 1.80.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers <pkg-gnome-maintain...@lists.alioth.debian.org> Changed-By: Jeremy Bícha <jbi...@ubuntu.com> Closes: 1065332 1066032 1066900 Changes: gobject-introspection (1.80.1-2) unstable; urgency=medium . * Release to unstable . gobject-introspection (1.80.1-1) experimental; urgency=medium . [ Jeremy Bícha ] * New upstream release * Drop time_t and off_t patches: applied in new release . [ Simon McVittie ] * d/copyright: Remove unused license paragraph . gobject-introspection (1.80.0-2) experimental; urgency=medium . * Merge packaging changes from unstable: - d/p/girparser-Don-t-assume-sizeof-size_t-sizeof-void.patch, d/p/girparser-Make-sizes-in-integer_aliases-more-obviously-co.patch, d/p/girparser-Allow-time_t-off_t-etc.-to-appear-in-GIR-XML.patch, d/p/giscanner-treat-time_t-and-off_t-as-standalone-types.patch, d/p/tests-fix-the-tests-after-time_t-and-off_t-are-standalone.patch, d/p/tests-Add-coverage-for-off_t.patch: Add patches from upstream git to fix handling of time_t and off_t. Thanks to Shuyu Liu (Closes: #1066032) - d/emulated-g-ir-tool.in: Fix qemu-user invocation. Previously, this only worked on systems that could run the tool directly via binfmt_misc. * d/control: libgirepository1.0-dev requires GLib 2.80 data. Now that we are not building gir1.2-glib-2.0 locally, we shouldn't use ${binary:Version} to refer to it any more. Thanks: lintian * d/control: Bump required GLib version to 2.80.0. Now that GLib 2.80.0 is available, nobody should be using its development snapshots 2.79.x. * d/copyright: Update * Add a g-ir-inspect(1) man page * d/source/lintian-overrides: Add overrides for nogir profile name . gobject-introspection (1.80.0-1) experimental; urgency=medium . * New upstream stable release * Merge packaging changes from unstable - dh_girepository: Avoid generating a dependency on libgirepository1.0-dev (Closes: #1065332) - Use host g-ir-compiler (possibly wrapped with qemu-user) when cross-compiling, since the build architecture g-ir-compiler has built-in knowledge of type sizes which is not necessarily correct for the host architecture (Closes: #1066900) - d/control: Make g-i explicitly depend on g-i-bin, not just via a virtual package, as requested by Matthias Klose on #1064369. This might possibly help autopkgtest to provide better pinning. - d/rules: Base the choice of -Dbuild_introspection_data on whether we are building gir1.2-*, not the nogir build profile specifically * Refresh patch series . gobject-introspection (1.79.1-1) experimental; urgency=medium . * New upstream release * Bump minimum glib to 2.79.0 * Add gir1.2-glib-2.0-dev to Build-Depends * Drop gir1.2-glib-2.0 & gir1.2.0-glib-dev: Now built by glib2.0 * Drop 3 patches applied in new release Checksums-Sha1: 0ef4df2458112547a991f9f0c86d9c9108eb95f5 4044 gobject-introspection_1.80.1-2.dsc 4ca712e70ec93f706150b886c6e29a994fbcae3d 56948 gobject-introspection_1.80.1-2.debian.tar.xz c56ad8625205e5d8a0f4507dbc6d358b68077366 10801 gobject-introspection_1.80.1-2_source.buildinfo Checksums-Sha256: b669c328dafbd7bfc491aa63bc300ed69758af7817e3d8ac7bb998b531de0a5c 4044 gobject-introspection_1.80.1-2.dsc b512c6fd195f37c7cced3bcb30ddff4992adf1afcb09c3569d89e2ae8d3142e0 56948 gobject-introspection_1.80.1-2.debian.tar.xz 0e25f3e28d2eb83ea5d8d55903c29a7251c95745a450e697100eb7cbe2aa111c 10801 gobject-introspection_1.80.1-2_source.buildinfo Files: 26cf42a54a9401d3c77a72c84a1d1eca 4044 devel optional gobject-introspection_1.80.1-2.dsc 56ab8ad92bfb4c98ea6e7625aceae039 56948 devel optional gobject-introspection_1.80.1-2.debian.tar.xz 9b11caa6a58a98f8c449456a7241b110 10801 devel optional gobject-introspection_1.80.1-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmY2ZVoACgkQ5mx3Wuv+ bH3TCw/+LBsupuU7YoxAKQ9KTRqbGi58mZEXNCxKHSxEvncjSZhtP5SEeeklAv1w FBsGnwlPZrx2DtOvYV4KeunpqBQoiczG9gXxrxDGvjDq9AL6TL+hBhNAoRmxUI+g QLZ2rNIWSTYBp44QPGtahkOOrKwMBAWFl2KSXOcyrCirkt5nrlOZgY374aRo39nX ie1Hi8TY1IVBITWwLasNBdCecSH8F79lKXxKQYy/p4vX1/dz7qTftGHp797bj6QA xceo9sqMLEirRXeTC1vii2CHYtFFuRko6iC7+zBmZxofjinKwm5PvDnGk9sKG40F fSQcfX0nPENlBAqNY3HZm3J0ffhho46ZBKeVZAyQBTXmevZLbfTYZKQWLc6Lvsv2 OAtaUTOwaXn1LyDe4cumLKrJJ2P9Grfr5GGqQaBl1Jhx0Ij8vi01MLnWcYzoR2Mm 35cayVrEUt13TT9zjpZR6kZEIJj9fq0sSBUDyT48EVvbPb61mqvsrJdtl9Z/KkXt pPMJlb5rbI8fILIrBruL34LtHIqxCjr0yeimIw8ciKmrQz2L9fX5aG7MJ1msX7dV op+i9e7mAO0x9B8YdsLaKt+dkf55XaHGmRZJS2ccbGus9G5ZgGp2I5McuW371Frt yccGK9J0IohgQT3pMOPUoOfdwH9ISHUJB4qprX0FC7w5S59mZgo= =mswX -----END PGP SIGNATURE-----
pgpyK9SeMP6a8.pgp
Description: PGP signature
--- End Message ---
