Description of problem: Firstly I filed against python-qtconsole as https://bugzilla.redhat.com/show_bug.cgi?id=1753060 as this affects Astronomy-KDE spin compose, however as it turns out sip-4.19.18-7.fc32 change affects more packages, I also file against sip. sip-4.19.18-7.fc32 dropped python3-sip, which makes 7 packages uninstallable on rawhide: $ dnf repoquery --disablerepo=\* --enablerepo=koji-32 --qf "%{name}-%{version}-%{release}.%{arch}\t\t%{sourcerpm}" --whatrequires python3-sip frescobaldi-3.0.0-11.fc32.noarch frescobaldi-3.0.0-11.fc32.src.rpm gns3-gui-2.1.16-4.fc32.noarch gns3-gui-2.1.16-4.fc32.src.rpm python3-arcus-lulzbot-3.6.18-2.fc32.x86_64 libarcus-lulzbot-3.6.18-2.fc32.src.rpm python3-krop-0.5.1-5.fc32.noarch krop-0.5.1-5.fc32.src.rpm python3-poppler-qt5-0.24.2-14.fc32.x86_64 python3-poppler-qt5-0.24.2-14.fc32.src.rpm python3-pyface-qt-6.1.2-1.fc32.noarch python-pyface-6.1.2-1.fc32.src.rpm python3-qtconsole-4.5.5-1.fc32.noarch python-qtconsole-4.5.5-1.fc32.src.rpm
Looks like a bunch of packages had incorrect deps. Good thing, so they can bq.je fixed
So, 2 concrete problems in general: 1. Packages should not depend on python*-sip (or namespaced variants like python3-pyqt5-sip) directly. Applications that generate bindings with sip should include a snippet similar to: %{?_sip_api:Requires: python3-pyqt5-sip-api(%{_sip_api_major}) >= %{_sip_api}} 2. Applications should not depend on non-namespaced python3-sip, but use python3-pyqt5-sip (or other variants as appropriate). I'll try to review all the offenders, looks like most of them can move to use PyQt5.sip instead.
All affected packages now are either fixed or have bugs filed awaiting upstream feedback on how best to proceed
Also note that nothing obsoletes python3-sip.
Obsoletes were added in latest rawhide builds, https://src.fedoraproject.org/rpms/sip/c/8fd958b1a4ffa6e6bd539032eba9eaeb6b70dc9e
I think it's reasonable to obsolete the package from f-o-p too. Added to latest build.
Will these fixes be available in fc31 also?
You should direct that question to the maintainer(s) of the components in question. This bug has several linked already to track them, enki : bug #1752766 frescobaldi : bug #1753266 krop : bug #1707034 python-pyface : bug #1753414 python-qtconsole : bug #1753060 Which one(s) were you inquiring about? or something else?
(In reply to Rex Dieter from comment #8) > You should direct that question to the maintainer(s) of the components in > question. This bug has several linked already to track them, (...) > Which one(s) were you inquiring about? or something else? frescobaldi : bug #1753266 I will comment there. Thanks.
I've got a not-installable bug report (bug #1904473) for the veusz package. Veusz uses sip to build some PyQt code. The problem is that in rawhide veusz requires python3.9dist(sip), which is not provided by anything. To fix the bug I tried changing the sip api snippet to what was suggested above: -%{?_python3_sip_api:Requires: sip-api(%{_python3_sip_api_major}) >= %{_python3_sip_api}} +%{?_sip_api:Requires: python3-pyqt5-sip-api(%{_sip_api_major}) >= %{_sip_api}} Building in mock for rawhide, this still adds a requirement on python3.9dist(sip). I don't have any explicit sip requirements, except for the build. Is this related to this bug, or is this something else? Any suggestions for fixing this would be great.
No, it is related to bz1825507. Let's followup in bz1904473.
FEDORA-2023-a5b7b6b33a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a5b7b6b33a
FEDORA-2023-a5b7b6b33a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a5b7b6b33a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a5b7b6b33a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-a5b7b6b33a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.