On Thu, 11 Aug 2022, Ole Streicher wrote:

Hi,

I have a package

https://salsa.debian.org/debian-astro-team/asdf-standard

that changed its build process to pyproject.toml. As hinted by pybuild,
I added pybuild-plugin-pyproject to the build dependencies; however it
still does not build properly. The build fails with the following
output:

-------------------------------8<-----------------------------------
* Building wheel...
Successfully built UNKNOWN-1.0.3-py3-none-any.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.10 with "installer" module
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?
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit code 13
make: *** [debian/rules:5: binary] Error 25 -------------------------------8<-----------------------------------

which I do not understand. The build backend specified in pyproject.toml is

build-backend = "setuptools.build_meta"

What goes wrong here?

Full build log:

https://salsa.debian.org/debian-astro-team/asdf-standard/-/jobs/3095942

I *think* the issue might be that our setuptools is too old to understand
how to get project metadata from pyproject.toml (PEP 621). This seems to indicate that it was added in setuptools 61.0.0:

https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html

As a workaround, you might try to patch the metadata back into setup.cfg?

Scott

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

I have a package

https://salsa.debian.org/debian-astro-team/asdf-standard

that changed its build process to pyproject.toml. As hinted by pybuild,
I added pybuild-plugin-pyproject to the build dependencies; however it
still does not build properly. The build fails with the following
output:

-------------------------------8<-----------------------------------
* Building wheel...
Successfully built UNKNOWN-1.0.3-py3-none-any.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for python3.10 with "installer" module
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?
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit code 13
make: *** [debian/rules:5: binary] Error 25 -------------------------------8<-----------------------------------

which I do not understand. The build backend specified in pyproject.toml is

build-backend = "setuptools.build_meta"

What goes wrong here?

Full build log:

https://salsa.debian.org/debian-astro-team/asdf-standard/-/jobs/3095942

Cheers

Ole

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Scott (2022.08.11_21:57:04_+0000)

I *think* the issue might be that our setuptools is too old to understand
how to get project metadata from pyproject.toml (PEP 621). This seems to indicate that it was added in setuptools 61.0.0:

https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html

Yep, I just saw this in another package, too.

SR

--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Scott Talbert <swt@techie.net> writes:

On Thu, 11 Aug 2022, Ole Streicher wrote:

-------------------------------8<-----------------------------------
* Building wheel...
Successfully built UNKNOWN-1.0.3-py3-none-any.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for
python3.10 with "installer" module
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?
dh_auto_build: error: pybuild --build -i python{version} -p 3.10
returned exit code 13
make: *** [debian/rules:5: binary] Error 25
-------------------------------8<-----------------------------------

I *think* the issue might be that our setuptools is too old to
understand how to get project metadata from pyproject.toml (PEP 621).
This seems to indicate that it was added in setuptools 61.0.0:

https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html

As a workaround, you might try to patch the metadata back into setup.cfg?

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).

Cheers

Ole

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 12 Aug 2022, Ole Streicher wrote:

Scott Talbert <swt@techie.net> writes:

On Thu, 11 Aug 2022, Ole Streicher wrote:

-------------------------------8<-----------------------------------
* Building wheel...
Successfully built UNKNOWN-1.0.3-py3-none-any.whl
I: pybuild plugin_pyproject:118: Unpacking wheel built for
python3.10 with "installer" module
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?
dh_auto_build: error: pybuild --build -i python{version} -p 3.10
returned exit code 13
make: *** [debian/rules:5: binary] Error 25
-------------------------------8<-----------------------------------

I *think* the issue might be that our setuptools is too old to
understand how to get project metadata from pyproject.toml (PEP 621).
This seems to indicate that it was added in setuptools 61.0.0:

https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html

As a workaround, you might try to patch the metadata back into setup.cfg?

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?

Scott

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)