Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Ole Streicher <olebole@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: pybuild pyproject.toml problem
Date: Fri, 12 Aug 2022 21:10:01 +0200
Message-ID: <ETIcF-9eq-1@gated-at.bofh.it>
References: <ETnUB-hy0W-1@gated-at.bofh.it> <EToxj-hytx-5@gated-at.bofh.it> <ETCAh-5VD-15@gated-at.bofh.it> <ETEC5-75x-3@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Fri Aug 12 19:00:10 2022
Old-Return-Path: <news@liska.ath.cx>
X-Amavis-Spam-Status: No, score=-6.361 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.25, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5.5
X-Greylist: delayed 78000 seconds by postgrey-1.36 at bendel; Fri, 12 Aug 2022 18:44:43 UTC
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Lines: 22
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/20172
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/87sfm18fop.fsf@orrococo
Approved: robomod@news.nic.it
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Fri, 12 Aug 2022 20:44:38 +0200
X-Original-Message-ID: <87sfm18fop.fsf@orrococo>
X-Original-References: <87sfm2pk4x.fsf@orrococo> <alpine.DEB.2.22.394.2208111754020.36944@bear.techie.net> <87edxlpr8t.fsf@orrococo> <alpine.DEB.2.22.394.2208121109430.50941@bear.techie.net>
Xref: csiph.com linux.debian.maint.python:14338

Scott Talbert <swt@techie.net> writes:
> On Fri, 12 Aug 2022, Ole Streicher wrote:
>> Scott Talbert <swt@techie.net> writes:
>>> On Thu, 11 Aug 2022, Ole Streicher wrote:
>>>> E: pybuild pybuild:369: build: plugin pyproject failed with: UNKNOWN
>>>> wheel found: UNKNOWN-1.0.3-py3-none-any.whl. Does pyproject.toml
>>>> specify a build-backend?
>>>
>>> I *think* the issue might be that our setuptools is too old to
>>> understand how to get project metadata from pyproject.toml (PEP 621).
>>
>> Since setuptools 63 is already in experimental, I will probably just
>> wait until it makes its way to unstable (and file a bug for it).
>
> Does building with setuptools from experimental resolve the issue?

Yes, I can confirm that it builds with the version from experimental
(63.2.0-1) without other changes.

Cheers

Ole