Groups > linux.debian.maint.python > #14277

Re: Build and run-time triplets

From	Andrey Rahmatullin <wrar@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Build and run-time triplets
Date	2022-07-24 21:50 +0200
Message-ID	<EMPLY-dA1E-3@gated-at.bofh.it> (permalink)
References	(2 earlier) <Ewl5v-3Cb5-7@gated-at.bofh.it> <EwloR-3Cz8-5@gated-at.bofh.it> <EMNK9-dyR6-5@gated-at.bofh.it> <EMOPT-dzto-9@gated-at.bofh.it> <EMPCi-dzYl-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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

Thread

Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-06-08 23:50 +0200
  Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-06-09 08:30 +0200
    Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-06-09 09:50 +0200
      Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-06-09 10:10 +0200
        Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-06-09 11:00 +0200
          Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-06-09 12:00 +0200
          Re: Build and run-time triplets Simon McVittie <smcv@debian.org> - 2022-06-09 12:10 +0200
            Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-06-09 12:50 +0200
        Re: Build and run-time triplets Simon McVittie <smcv@debian.org> - 2022-06-09 11:30 +0200
          Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-06-09 11:50 +0200
            Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-06-09 12:10 +0200
              Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-06-09 12:50 +0200
        Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-07-24 19:40 +0200
          Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-07-24 20:50 +0200
            Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-07-24 21:30 +0200
          Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-07-24 20:50 +0200
            Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-07-24 21:40 +0200
              Re: Build and run-time triplets Andrey Rahmatullin <wrar@debian.org> - 2022-07-24 21:50 +0200
                Re: Build and run-time triplets Julian Gilbey <julian@d-and-j.net> - 2022-07-24 23:10 +0200

csiph-web