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:
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
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
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.
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.