[3dprinter-general] Bug#1133406: Bug#1133406: python3-pynest2d fails to coinstall

Helmut Grohne helmut at subdivi.de
Mon Apr 13 12:12:10 BST 2026


Hi Gregor,

On Mon, Apr 13, 2026 at 12:56:47PM +0200, Gregor Riepl wrote:
> 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:

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.

> 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

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



More information about the 3dprinter-general mailing list