Bug#954764: g-ir-scanner produces subtly different /usr/share/gir-1.0/GMime-3.0.gir on different architectures

[Daniel Kahn Gillmor]

Package: gobject-introspection
Version: 1.62.0-5+b1
Control: affects -1 + libgmime-3.0-dev

The multi-arch hinter suggested back in gmime 3.2.6 that
libgmime-3.0-dev could be Multi-arch: same, which i think is correct.

However, after gmime 3.2.7-1 was built on different build daemons, it
appears that GMime-3.0.gir is generated with different line number
offsets:

--- libgmime-3.0-dev_3.2.7-1_amd64.deb
+++ libgmime-3.0-dev_3.2.7-1_armhf.deb
[…]
│ │ ├── ./usr/share/gir-1.0/GMime-3.0.gir
│ │ │ @@ -9110,33 +9110,33 @@
│ │ │             parent="CryptoContext"
│ │ │             glib:type-name="GMimeGpgContext"
│ │ │             glib:get-type="g_mime_gpg_context_get_type"
│ │ │             glib:type-struct="GpgContextClass">
│ │ │        <doc xml:space="preserve"
│ │ │             filename="gmime-gpg-context.c"
│ │ │             line="61">A GnuPG crypto context.</doc>
│ │ │ -      <source-position filename="gmime-gpg-context.h" line="37"/>
│ │ │ +      <source-position filename="gmime-gpg-context.h" line="36"/>
│ │ │        <constructor name="new" c:identifier="g_mime_gpg_context_new">
│ │ │          <doc xml:space="preserve"
│ │ │               filename="gmime-gpg-context.c"
│ │ │               line="388">Creates a new gpg crypto context object.</doc>
│ │ │ -        <source-position filename="gmime-gpg-context.h" line="42"/>
│ │ │ +        <source-position filename="gmime-gpg-context.h" line="41"/>
│ │ │          <return-value transfer-ownership="full">
│ │ │            <doc xml:space="preserve"
│ │ │                 filename="gmime-gpg-context.c"
│ │ │                 line="393">a new gpg crypto context object.</doc>
│ │ │            <type name="CryptoContext" c:type="GMimeCryptoContext*"/>
│ │ │          </return-value>
│ │ │        </constructor>
│ │ │      </class>
│ │ │      <record name="GpgContextClass"
│ │ │              c:type="GMimeGpgContextClass"
│ │ │              disguised="1"
│ │ │              glib:is-gtype-struct-for="GpgContext">
│ │ │ -      <source-position filename="gmime-gpg-context.h" line="37"/>
│ │ │ +      <source-position filename="gmime-gpg-context.h" line="36"/>
│ │ │      </record>
│ │ │      <function-macro name="HEADER"
│ │ │                      c:identifier="GMIME_HEADER"
│ │ │                      introspectable="0">
│ │ │        <source-position filename="gmime-header.h" line="33"/>
│ │ │        <parameters>
│ │ │          <parameter name="obj">

note that the files gmime-gpg-context.h does *not* differ on any of the
platforms (that file ships in libgmime-3.0-dev, and there is no
difference between the different architectures).

Note that the line numbers listed in the .gir file are correct on amd64,
while the armhf line numbers appear to be off-by-one.

GMime-3.0.gir is built with g-ir-scanner, which is why i'm assigning
this bug report to the gobject-introspection package.

Here are the build logs, which show that both builds used
gobject-introspection 1.62.0-5+b1:

https://buildd.debian.org/status/fetch.php?pkg=gmime&arch=armhf&ver=3.2.7-1&stamp=1584858058&raw=0
https://buildd.debian.org/status/fetch.php?pkg=gmime&arch=amd64&ver=3.2.7-1&stamp=1584858490&raw=0

If the problem is some other underlying element of the toolchain, feel
free to reassign!

Thanks for maintaining gobject-introspection in debian!

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20200323/a0a052c8/attachment.sig>