Bug 296508 - emulators/py-qemu.qmp: py312-setuptools_scm7-7.1.0 conflicts with py312-setuptools-scm-9.2.2
Summary: emulators/py-qemu.qmp: py312-setuptools_scm7-7.1.0 conflicts with py312-setup...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Muhammad Moinur Rahman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-07-04 12:02 UTC by O. Hartmann
Modified: 2026-07-11 20:25 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (bofh)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description O. Hartmann 2026-07-04 12:02:28 UTC
On recent CURRENT running most recent ports tree, the build of port emulators/py-qemu.qmp fails with the error:

[...]
adding 'setuptools_scm-7.1.0.dist-info/RECORD'
removing build/bdist.freebsd-16.0-CURRENT-amd64/wheel
Successfully built setuptools_scm-7.1.0-py3-none-any.whl
===>  Staging for py312-setuptools_scm7-7.1.0
===>   py312-setuptools_scm7-7.1.0 depends on package: py312-packaging>=20.0 - found
===>   py312-setuptools_scm7-7.1.0 depends on package: py312-typing-extensions>=0 - found
===>   py312-setuptools_scm7-7.1.0 depends on file: /usr/local/bin/python3.12 - found
===>   Generating temporary packing list
====> Compressing man pages (compress-man)
===>  Installing for py312-setuptools_scm7-7.1.0
===>  Checking if py312-setuptools_scm7 is already installed
===>   Registering installation for py312-setuptools_scm7-7.1.0 as automatic
Installing py312-setuptools_scm7-7.1.0...
pkg-static: py312-setuptools_scm7-7.1.0 conflicts with py312-setuptools-scm-9.2.2 (installs files into the same place).  Problematic file: /usr/local/lib/python3.12/site-packages/setuptools_scm/__init__.py
*** Error code 1

The port devel/py-setuptoosl-scm (9.2.2) is required by devel/py-hatch-vcs.
Comment 1 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2026-07-11 20:25:28 UTC
I think I have fixed this while upgrading the port. But reopen if it's not fixed yet.