Summary: | >=app-text/calibre-0.9.38 - src_install(): RuntimeError: the sip module implements API v10.0 but the PyKDE4.kdeui module requires API v9.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabiano <fabianoengler> |
Component: | Current packages | Assignee: | Zac Medico <zmedico> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | datty.wtb, fabianoengler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
calibre-0.9.39 build log
calibre-0.9.38 build log |
Description
Fabiano
2013-07-20 06:29:10 UTC
Created attachment 353690 [details]
calibre-0.9.39 build log
Created attachment 353692 [details]
calibre-0.9.38 build log
This is covered by sip upgrade notice. I don't know if subslots could improve the situation here. ...Ah, correction (I'm a bit out of touch): PyQt4 does handle it by sip subslots now. However the change isn't propagated down the tree, so it seems an explicit sip subslot dependency is needed here. Just had this happen to me....I normally stay away from python stuff, but every six months or so I do need to upgrade kde and calibre....would be nice if calibre could depend on something that keeps pyqt and pykde in sync... File "/usr/lib64/python2.7/site-packages/PyQt4/uic/__init__.py", line 175, in compileUi winfo = compiler.UICompiler().compileUi(uifile, pyfile, from_imports, resource_suffix) File "/usr/lib64/python2.7/site-packages/PyQt4/uic/Compiler/compiler.py", line 55, in __init__ CompilerCreatorPolicy()) File "/usr/lib64/python2.7/site-packages/PyQt4/uic/uiparser.py", line 127, in __init__ self.factory = QObjectCreator(creatorPolicy) File "/usr/lib64/python2.7/site-packages/PyQt4/uic/objcreator.py", line 97, in __init__ self._cwFilters.append(plugin_locals["getFilter"]()) File "<string>", line 22, in getFilter RuntimeError: the sip module implements API v10.0 but the PyKDE4.kdeui module requires API v8.1 * ERROR: app-text/calibre-1.2 failed (install phase): * (no error message) *** This bug has been marked as a duplicate of bug 336368 *** |