Bug 2259003 - libolm: FTBFS with python-setuptools 69.0.3 in Fedora Rawhide
Summary: libolm: FTBFS with python-setuptools 69.0.3 in Fedora Rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libolm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: marcdeop
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F40FTBFS 2250718
TreeView+ depends on / blocked
 
Reported: 2024-01-18 15:09 UTC by Karolina Surma
Modified: 2024-02-06 21:08 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-02-06 21:08:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2024-01-18 15:09:32 UTC
Description of problem:
Package libolm fails to build from source python-setuptools 69.0.3 in Fedora Rawhide.

Version-Release number of selected component (if applicable):
'3.2.15-4'

See logs:
https://download.copr.fedorainfracloud.org/results/ksurma/setuptools-69.0.3:custom:isolated/fedora-rawhide-x86_64/06907139-libolm/builder-live.log.gz

/usr/lib/python3.12/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 = 'Apache 2.0'`

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

Additional info:
This seems to have been resolved upstream in version 3.2.16. Please consider updating the package.

Reproducible: Always


Note You need to log in before you can comment on or make changes to this bug.