python3-pynest2d is declared Multi-Arch: same, but fails to coinstall.

The file /usr/lib/python3/dist-packages/pynest2d.pyi is shared by
python3-pynest2d/5.0.0-3+b6 as present in forky|unstable with varying
content.

Please ensure that shared files have bit-identical content across
architectures, move architecture-dependent files to
architecture-dependent paths or remove the Multi-Arch: same field.

Kind regards

Helmut Grohne

Hello Helmut,

These packages are supposed to be co-installable, and the file in question should be identical across architectures. However, it _is_ an autogenerated file and that increases the risk of mismatches when the generator doesn't behave exactly the same.

I just verified this, and the file is in fact identical between release architectures amd64, arm64 and ppc64el.
riscv64 doesn't match, because it was built with a different SIP version:

--- pynest2d.pyi.amd64  2025-12-06 00:45:50.000000000 +0100
+++ pynest2d.pyi.riscv64        2025-12-08 03:09:28.000000000 +0100
@@ -1,6 +1,6 @@
  # The PEP 484 type hints stub file for the pynest2d module.
  #
-# Generated by SIP 6.14.0
+# Generated by SIP 6.15.0

There are no other mismatched lines in the file.

This should be easy to fix - I committed a patch that removes the version info from the file:
https://salsa.debian.org/3dprinting-team/pynest2d/-/commit/8b0765177ff8f9de8a84d38146875ebed86060d7

@myon Could you upload 5.0.0-4 when you have time?
Thank you!

Regards,
Gregor

Hi Gregor,

Thanks for tracking this down. This tends to be a rare problem, because
usually packages get built with roughly the same versions of
dependencies. riscv64 was lagging behind a a bit and delayed some
builds. Its task queue is now below 3 hours.

The question I have here is whether the cure is better than the disease
here. If we simply remove the version, there is no flagging of different
versions being used. Therefore, bugs can become subtly
architecture-specific. This may make debugging them harder. We don't
technically need the version information as it is recorded in the
.buildinfo.

So another way to resolve this would be asking the release team for a
binNMU with the expectation that such a version difference is rare.

You're the domain expert here, so I trust your choice here.

Helmut

Hi Helmut,

I don't think we will lose much by removing the version comment and keeping the file as multi-arch=same.

If there's ever a situation where SIP generates different .pyi files (essentially a Python interface to the native library in this case) across different versions, it may actually indicate a real problem. The version comment alone doesn't really do that.

As for making debugging harder - I don't think this is much of an issue either.
Since pynest2d is a native library with a Python interface, it would need to be debugged on the target architecture or with qemu-user anyway.

Regards,
Gregor

We believe that the bug you reported is fixed in the latest version of
pynest2d, 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 1133406@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated pynest2d 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: Tue, 28 Apr 2026 14:11:12 +0000
Source: pynest2d
Architecture: source
Version: 5.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages <3dprinter-general@lists.alioth.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 1133406
Changes:
 pynest2d (5.0.0-4) unstable; urgency=medium
 .
   [ Gregor Riepl ]
   * Remove version info from pynest2d.pyi to avoid differences
     when the package us build with different SIP versions on
     different architectures. Closes: #1133406
 .
   [ Christoph Berg ]
   * B-D on pkgconf.
Checksums-Sha1:
 840303edc3721b720b3bd4437b6a60f2f49a8934 2115 pynest2d_5.0.0-4.dsc
 13651627d1c170d52f4aa0c7f544b6401eedcdd0 4768 pynest2d_5.0.0-4.debian.tar.xz
Checksums-Sha256:
 e394b76a1600ece2baf97100dbebe30398bb9e7bedd5175eac6fb51522bc0b0e 2115 pynest2d_5.0.0-4.dsc
 76a1d5f5328ed628ff8550b896f02107ebd42bd93048f116f9dc4cb89f1a030b 4768 pynest2d_5.0.0-4.debian.tar.xz
Files:
 81a73ff2ba9b5eab0fff9aae6507dcae 2115 libs optional pynest2d_5.0.0-4.dsc
 610b19161d462364d26ea5461e81f566 4768 libs optional pynest2d_5.0.0-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmnwwCoACgkQTFprqxLS
p65LJA/+Jmb8BoGQeKxSVKeEI98K2XJJfDQaT+W80t9gxiUZTMI/8aZVTn45QZv1
nleP1V8d8qqjuB7F6OLk2h5ywoeFIcOWZhyKB44Cp6b/2RZZ/8vUaXMXM4co+vxx
YS9kZT7KX8C82JYplt5Hfy1E+KlkUn99VXvfBTl87BBdn124Ay3Rzgg1lluhfLUT
n0UV0u0IEIgQdMWpU6CWK/Ja/UsGfY8/V8RXleRUzAqoOQFIZIdR5ZC+Ps+QdWTJ
q68sL6jGB6BKnmTTCXRZQ2/5P8zAoSt9RxmLDSX90CAvy033Z7OmvNqaF/IdPekF
USgmm1B/TTuNqn/yeHJgdMeIz6VrY9Zt8D2bEl24XSHFgWZjODB+303zU4azydXH
/Qp8S5LwBzvAa0tcUomi1nBhAmqQGfcD2tl6ZbS/KG02s7Dtj2RiMfWOLAI0fC99
ZUcR4os0L+tETa3rIOIa19SPGIAb03sq3nz8Q6DOo04DuYDp9y0KS03ZvGQBfa/G
trN1lyadqsTObXxQ0UBGSrtvP4OsDy8vUVp1bh9RAnLXNsdquf+SO6eJCuOIL4p6
LFzqQj7CIMYzayPnCZRxJIVUVdjL/t3edmOAbPrEy50UZMjlna4JHGrUdqEVji4i
31rAiS7hc3iPodoWktWJglX+948K0/CjRM8Ee/uKE2QDOppphOM=
=Up5R
-----END PGP SIGNATURE-----

Oops, that should have said "is built".