Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 922971 - dev-python/autocommand-2.2.2 setup license error
Summary: dev-python/autocommand-2.2.2 setup license error
Status: RESOLVED DUPLICATE of bug 917754
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-26 17:55 UTC by Tomasz Chilinski
Modified: 2024-02-06 03:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
fixes setup phase error (autocommand-2.2.2-setup-license-fix.patch,339 bytes, patch)
2024-01-26 17:55 UTC, Tomasz Chilinski
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Chilinski 2024-01-26 17:55:30 UTC
Created attachment 883190 [details, diff]
fixes setup phase error

We have during setup phase:

/usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:75: _MissingDynamic: `license` defined outside of `pyproject.toml` is ignored.
!!

        ********************************************************************************
        The following seems to be defined outside of `pyproject.toml`:

        `license = 'LGPLv3'`

        According to the spec (see the link below), however, setuptools CANNOT
        consider this value unless `license` is listed as `dynamic`.

        https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

        To prevent this problem, you can list `license` under `dynamic` or alternatively
        remove the `[project]` table from your file and rely entirely on other means of
        configuration.
        ********************************************************************************

!!


Attached patch fixes it.
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-06 03:35:57 UTC

*** This bug has been marked as a duplicate of bug 917754 ***