The License-File core metadata tag definition in https://peps.python.org/pep-0639/ was updated. Specifically: > Root License Directory (Short: License Directory) > The directory under which license files are stored in a project/distribution > and the root directory that their paths, as recorded under the License-File > core metadata fields, are relative to. Defined here to be the project root > directory for source trees and source distributions, and a subdirectory > named licenses of the directory containing the core metadata > (i.e., the .dist-info/licenses directory) for built distributions and > installed projects. And: > As specified by this PEP, [License-File] value is also that file’s path relative to the root license directory in [...] installed projects [...] Not supporting this means that despite hatch(ling) correctly marking files as License-Files, the macros don't mark them as such. We consider the files to be relative to the dist-info directory which is how it was before and AFAIk how setuptools does it. We need to update to the new behavior and ensure setuptools does that as well. As a transition period, we might add code that considers both approaches (relative to dist-info OR relative to dist-info/licenses).
setuptools RFE: https://github.com/pypa/setuptools/issues/3596
(In reply to Miro Hrončok from comment #0) > Not supporting this means that despite hatch(ling) correctly marking files > as License-Files, the macros don't mark them as such. Thanks for following up on this.
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/326
FEDORA-2022-8e5db6b83a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e5db6b83a
FEDORA-2022-8e5db6b83a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-190d3df912 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-190d3df912
FEDORA-2022-c4d503f53c has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c4d503f53c
FEDORA-2022-c8124fba28 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c8124fba28
FEDORA-2022-190d3df912 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-190d3df912` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-190d3df912 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-c4d503f53c has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c4d503f53c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c4d503f53c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-c8124fba28 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c8124fba28` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c8124fba28 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-190d3df912 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-c8124fba28 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-c4d503f53c has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.