Bug 2453823

Summary: flatpak-module-tools fails to build with setuptools_scm 10+
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: flatpak-module-toolsAssignee: Yaakov Selkowitz <yselkowi>
Status: ASSIGNED --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: kalevlember, otaylor, yselkowi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2412434, 2433833, 2451398    

Description Miro Hrončok 2026-04-01 12:14:47 UTC
We are trying to python-setuptools_scm to version 10.x

https://src.fedoraproject.org/rpms/python-setuptools_scm/pull-request/39


This package fails to build with:

error: Installed (but unpackaged) file(s) found:
   /usr/lib/python3.14/site-packages/VERSION

https://copr.fedorainfracloud.org/coprs/churchyard/vcs-versioning/package/flatpak-module-tools/



See https://setuptools-scm.readthedocs.io/en/latest/changelog/#1000-2026-02-26

"""
Version files (write_to and version_file) are now written to the build directory during build_py instead of the source tree during version inference. This enables installing packages from read-only source directories (e.g., Bazel builds).

Path transformation is automatically applied for src/ layouts - a configured path like src/mypackage/_version.py is correctly written to mypackage/_version.py in the build directory based on the package_dir configuration.

To restore the old behavior of writing version files at inference time (useful for development workflows), set the environment variable SETUPTOOLS_SCM_WRITE_TO_SOURCE=1. https://github.com/pypa/setuptools-scm/issues/1252
"""

Comment 1 Miro Hrončok 2026-04-16 09:42:54 UTC
Do you need help fixing this? Please respond.

Comment 2 Miro Hrončok 2026-04-17 12:14:30 UTC
Setting SETUPTOOLS_SCM_WRITE_TO_SOURCE=1 probably makes no difference, see my upstream report https://github.com/pypa/setuptools-scm/issues/1364

For now, perhaps rm -rf after %pyproject_install is a way to go.