When an upstream Python package has a runtime dependency on "sip": install_requires=['sip >=5.1, <6'] The RPM dependency generator generator creates something like: Requires: (python3.8dist(sip) >= 5.1 with python3.8dist(sip) < 6) However, no sip package in fedora provides python3dist(sip) or python3.8dist(sip).
I also get: ModuleNotFoundError: No module named 'sipbuild' No idea what sip package contains that module. (I'm trying to package PyQt-builder.)
I'm guessing these are upstream packages that still claim dependency on non-namespaced sip, see also bug #1753069 on why we chose to no longer ship that.
As for sipbuild, I'm guessing that may be part of sip v5, which we don't ship yet.
> I'm guessing these are upstream packages that still claim dependency on non-namespaced sip, see also bug #1753069 on why we chose to no longer ship that. I am aware of that BZ. Note that PyQt-builder is quite new software by the company behind PyQt, so the "still" in "still claim dependency on non-namespaced sip" sounds weird. Are we expected to patch all upstream packages that require "sip" not to do that? How do we approach upstream with this downstream problem? > As for sipbuild, I'm guessing that may be part of sip v5, which we don't ship yet. Sound legit, they do require sip >= 5.1. Thanks for more info.
Sounds like upstream is sending mixed messages? Though I just noticed now that 'python3.8dist(sip) >= 5.1' probably refers to sip v5 too, so maybe it's different there (compoared to sip v4)
Maybe. Let's revisit this once we update?
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
Any plans for sip 5? calibre-5.0 now requires it (and also is looking for sipbuild module, which seems to indeed only be in 5).
No immediate plans on my side, lack of time mostly. I fear implementing this may be a significant undertaking, in that it may not be safe to mix-n-match sip v4 and sipv5. If so, worst case we'll have to ensure the entire stack is moved to sip v5. (lots of rebuilds, and testing required)
If Rex and Than don't have time, I could probably take a stab at packaging sip5 as I'll need it for wxPython eventually. It seems that sip5 can be packaged alongside sip4, as at least Debian has done so.
Opened a review request for sip5 in case anyone wants to review it or comment on the packaging: https://bugzilla.redhat.com/show_bug.cgi?id=1891646