On Sun, Jul 24, 2022 at 08:30:42PM +0100, Julian Gilbey wrote: > On Sun, Jul 24, 2022 at 11:41:56PM +0500, Andrey Rahmatullin wrote: > > [...] > > > > > > I got all of the triplets working, but was then stymied when I tried > > > to specify Multi-Arch: same in the control file. I got a lintian > > > warning: multi-arch-same-package-calls-pycompile > > > It seems that since the pybuild system (via dh_python3) adds a > > > py3compile command to the postinst of the package, then I can't safely > > > use Multi-Arch: same. > > > > > > I don't know if this is the case for all python3 Arch: any packages > > > with compiled extensions; > > I think the tag desciption has a good step-by-step explanation why does > > the tag exists. > > But your package is not a "package with compiled extensions", is it? > > Yes, it's got compiled extensions (Cython) in addition to this > non-Python .so library file. > > > > are they all effectively Multi-Arch: no? Is this worth thinking about > > > in the longer term? > > What do you propose? > > I think the fix to bug #812228 might have done the job nicely ;-) If it actually ships extensions, the "it should usually get a dependency on the Python interpreter for the same architecture" part should still apply as far as I understand it.
-- WBR, wRAR
signature.asc
Description: PGP signature
