Bug 2301713

Summary:	pyside6-tools: dubious installation paths
Product:	[Fedora] Fedora	Reporter:	Ben Beasley <code>
Component:	python-pyside6	Assignee:	loise <loise>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	gui1ty, kde-sig, loise, priv.luk
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-pyside6-6.7.2-3.fc40	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-08-11 04:48:58 UTC	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:

Description Ben Beasley 2024-07-30 16:48:11 UTC

Description of problem:

In pyside6-tools, various subdirectories with Python libraries and even test suites are installed under /usr/bin/. This is very unusual and seems wrong.

Version-Release number of selected component (if applicable): 6.7.2-2.fc41


How reproducible:

$ repoquery --repo=rawhide -l pyside6-tools-0:6.7.2-2.fc41.x86_64

Actual results:


Last metadata expiration check: 0:04:22 ago on Tue 30 Jul 2024 12:40:23 PM EDT.
/usr/bin/android_deploy.py
/usr/bin/deploy.py
/usr/bin/deploy_lib
/usr/bin/deploy_lib/__init__.py
/usr/bin/deploy_lib/android
/usr/bin/deploy_lib/android/__init__.py
/usr/bin/deploy_lib/android/android_config.py
/usr/bin/deploy_lib/android/android_helper.py
/usr/bin/deploy_lib/android/buildozer.py
/usr/bin/deploy_lib/android/recipes
/usr/bin/deploy_lib/android/recipes/PySide6 
/usr/bin/deploy_lib/android/recipes/PySide6/__init__.tmpl.py
/usr/bin/deploy_lib/android/recipes/shiboken6
/usr/bin/deploy_lib/android/recipes/shiboken6/__init__.tmpl.py
/usr/bin/deploy_lib/commands.py
/usr/bin/deploy_lib/config.py
/usr/bin/deploy_lib/default.spec
/usr/bin/deploy_lib/dependency_util.py
/usr/bin/deploy_lib/deploy_util.py
/usr/bin/deploy_lib/nuitka_helper.py
/usr/bin/deploy_lib/pyside_icon.icns
/usr/bin/deploy_lib/pyside_icon.ico
/usr/bin/deploy_lib/pyside_icon.jpg
/usr/bin/deploy_lib/python_helper.py
/usr/bin/metaobjectdump.py
/usr/bin/project
/usr/bin/project.py
/usr/bin/project/__init__.py
/usr/bin/project/newproject.py
/usr/bin/project/project_data.py
/usr/bin/project/utils.py
/usr/bin/pyside_tool.py
/usr/bin/qml.py
/usr/bin/qtpy2cpp.py
/usr/bin/qtpy2cpp_lib
/usr/bin/qtpy2cpp_lib/astdump.py
/usr/bin/qtpy2cpp_lib/formatter.py
/usr/bin/qtpy2cpp_lib/nodedump.py
/usr/bin/qtpy2cpp_lib/qt.py
/usr/bin/qtpy2cpp_lib/tests
/usr/bin/qtpy2cpp_lib/tests/baseline
/usr/bin/qtpy2cpp_lib/tests/baseline/basic_test.cpp
/usr/bin/qtpy2cpp_lib/tests/baseline/basic_test.py
/usr/bin/qtpy2cpp_lib/tests/test_qtpy2cpp.py
/usr/bin/qtpy2cpp_lib/tokenizer.py
/usr/bin/qtpy2cpp_lib/visitor.py
/usr/bin/requirements-android.txt
/usr/lib/.build-id
/usr/lib/.build-id/f9
/usr/lib/.build-id/f9/c1c9edbc456d325e41ffb512b0117114d4fbd7
/usr/lib64/qt6/plugins/designer/libPySidePlugin.so
/usr/share/doc/pyside6-tools
/usr/share/doc/pyside6-tools/README.pyside6.md
/usr/share/doc/pyside6-tools/README.pyside6_addons.md
/usr/share/doc/pyside6-tools/README.pyside6_essentials.md
/usr/share/doc/pyside6-tools/README.pyside6_examples.md
/usr/share/licenses/pyside6-tools
/usr/share/licenses/pyside6-tools/Apache-2.0.txt
/usr/share/licenses/pyside6-tools/BSD-3-Clause.txt
/usr/share/licenses/pyside6-tools/GFDL-1.3-no-invariants-only.txt
/usr/share/licenses/pyside6-tools/GPL-2.0-only.txt
/usr/share/licenses/pyside6-tools/GPL-3.0-only.txt
/usr/share/licenses/pyside6-tools/LGPL-3.0-only.txt
/usr/share/licenses/pyside6-tools/LicenseRef-Qt-Commercial.txt
/usr/share/licenses/pyside6-tools/Qt-GPL-exception-1.0.txt

Expected results:

/usr/bin/ only contains entry points that belong on the system-wide PATH.

Additional info:

Comment 1 loise@kde.org 2024-07-30 17:58:57 UTC

Hi,

thank you for this report, which is why we didn't tag pyside6 for f40 in the first place :/  

Maybe you can help us find out what is the right solution according to your findings ?

I would be glad and appreciate every help to get this fixed, as it is also a known problem I couldn't solve.

BR, Loise

Comment 2 Fedora Update System 2024-08-02 21:16:25 UTC

FEDORA-2024-1e2816743b (python-pyside6-6.7.2-3.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-1e2816743b

Comment 3 Fedora Update System 2024-08-03 02:20:44 UTC

FEDORA-2024-1e2816743b has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1e2816743b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1e2816743b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2024-08-11 04:48:58 UTC

FEDORA-2024-1e2816743b (python-pyside6-6.7.2-3.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.