On Tuesday, February 1, 2022 6:01:22 AM EST Andreas Tille wrote:
> Am Sat, Jan 29, 2022 at 01:50:22AM +0500 schrieb Andrey Rahmatullin:
> > On Fri, Jan 28, 2022 at 09:48:00PM +0100, Andreas Tille wrote:
> > > Hi,
> > >
> > > I need python-subby as a new dependency for some Debian Med package.
> > >
> > > Unfortunately it does not build easily[1]:
> > > dh_auto_build -O--buildsystem=pybuild
> > >
> > > E: pybuild pybuild:367: build: plugin flit failed with: Neither
> > > [project] nor [tool.flit.metadata] found in pyproject.toml E: pybuild
> > > pybuild:367: build: plugin flit failed with: Neither [project] nor
> > > [tool.flit.metadata] found in pyproject.toml dh_auto_build: error:
> > > pybuild --build -i python{version} -p "3.10 3.9" returned exit code 13>
> > It indeed uses poetry, not flit, but you have export PYBUILD_SYSTEM=flit.
>
> Where can I find an example how to use poetry?
Add build-depends on pybuild-plugin-pyproject.
Drop build-depends on flit.
Drop the "export PYBUILD_SYSTEM=flit" line in d/rules.
The poetry build-depends I'm a little uncertain on. Subby has:
> [build-system]
> requires = ["poetry>=0.12"]
> build-backend = "poetry.masonry.api"
What I recall seeing is:
> [build-system]
> requires = ["poetry>=0.12"]
> build-backend = "poetry.core.masonry.api"
I am not familiar enough to know if that means that you need python3-poetry
(which you have) or if the upstream pyproject.toml is wrong and you need
poetry-core. Maybe someone else knows or you can experiment.
That should get you close.
Scott KAttachment:
signature.asc
Description: This is a digitally signed message part.