duplicate PY311 packages stops desktop build

[drsnx60]

WHile installing GNOME & KDE from Ports

py311-wheel-0.45.1 and py311-wheel-0.44.1
conflicts as both are used.

py311-setuptools_scm7-7.1.0 and py311-setuptools_scm-8.0.4
conflicts as both are used.

this results in that its necessary to uninstall and reinstall the other version of these Python packages while
building the desktops from ports.

Is it possible to get the Maintainers to use the same version of these python modules ?
The latest one , why would the previous module be used/required ?

 

[SirDice]

Solved Thread 'py311-wheel-0.45.1 conflicts with py311-wheel044-0.44.0 (installs files into the same place). Problematic file: /usr/local/bin/wheel-3.11'

Apr 10, 2025

Hello.
My system FreeBSD 14.2-RELEASE-p2 amd64
/etc/make.conf

CPUTYPE?=nocona
MAKE_JOBS_NUMBER=6

NO_GAMES=true
NO_INET6=true
NO_BLUETOOTH=true
NO_SHAREDOCS=true
OPTIONS_UNSET=DOCS X11 IPV6 BLUETOOTH GAMES SMB CUPS VULKAN FFMPEG GITWEB EXAMPLES

How to fix?

pkg-static: py311-wheel-0.45.1 conflicts with py311-wheel044-0.44.0 (installs files into the same place).  Problematic file: /usr/local/bin/wheel-3.11

# pkg version -v | egrep 'wheel'
py311-wheel044-0.44.0              =   up-to-date with index

# pkg version -v | egrep 'py'
py311-build-1.2.2_2...

• bagas
• Replies: 14
• Forum: Installation and Maintenance of Ports or Packages

 

[drsnx60]

Yes I understand it can be worked around and I have done so.
but allowing multiple versions of the same software to co-exist and obstruct for each other , is not beautiful or desired.

 

[SirDice]

but allowing multiple versions of the same software to co-exist and obstruct for each other , is not beautiful or desired.

With 33.000+ ports conflicts are bound to happen. Some applications require the 0.45.x version, some require the 0.44.x version. Probably due to some incompatible changes between 0.44 and 0.45 on this particular python module. It's not FreeBSD that doesn't allow both versions to co-exist, it's Python itself that prevents different versions of a module to co-exist. Try using pip(3) and install two different versions of the same module to see what happens.

With Ruby gems for example you often can install multiple versions of the same module. Not always possible but for most gems it's not a problem.