FS#41103 - [python-qscintilla] packages need rebuild

Attached to Project: Arch Linux
Opened by kachelaqa (kachelaqa) - Saturday, 05 July 2014, 16:43 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 07 August 2014, 19:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No

Details

Description:

The python/python2 qscintilla packages cannot be used unless they are rebuilt against the recent new versions of sip/pyqt.

This problem seems to regularly happen when the pyqt/sip packages are updated. Would it be possible to ensure the python qscintilla packages are always automatically re-built at the same time?

Additional info:
qscintilla - 2.8.3-1
pyqt - 4.11.1-1
sip - 4.16.2-1

Steps to reproduce:

>>> from PyQt4 import Qsci
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: /usr/lib/python3.4/site-packages/PyQt4/Qsci.so: undefined symbol: _ZTI11QsciPrinter
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Thursday, 07 August 2014, 19:09 GMT
Reason for closing:  Fixed
Additional comments about closing:  qscintilla 2.8.3-4
Comment by kachelaqa (kachelaqa) - Thursday, 10 July 2014, 09:04 GMT
The fix did not work - i.e. the same error is given when attempting to import the Qsci module. (PS: When I do a local rebuild, the error goes away).
Comment by Ray Rashif (schivmeister) - Thursday, 10 July 2014, 09:05 GMT
I can confirm this as eric is failing to build for the same reason.
Comment by Andrea Scarpino (BaSh) - Thursday, 10 July 2014, 15:54 GMT
Uh? qscintilla has already benn rebuilt upon newer pyqt.

python-pyqt4 Build Date: 2014-07-04 13:37 UTC
qscintilla Build Date: 2014-07-05 17:14 UTC
Comment by kachelaqa (kachelaqa) - Thursday, 10 July 2014, 16:08 GMT
Yes, of course I tried the newest packages (and just did so again to make sure), and the error is still there.
Comment by Massimiliano Torromeo (mtorromeo) - Thursday, 10 July 2014, 16:26 GMT
I confirm that the error is still present, but in my case a local rebuild (in a clean chroot) did not fix it.
Test with this: python2 -c 'from PyQt4 import Qsci'
Comment by kachelaqa (kachelaqa) - Thursday, 10 July 2014, 16:51 GMT
@Massimiliano
Just to be clear - did you rebuild all the packages (i.e. python-qscintilla, python2-qscintilla, python-qscintilla-common and qscintilla)?
Comment by Massimiliano Torromeo (mtorromeo) - Thursday, 10 July 2014, 18:22 GMT
Yes, I built and reinstalled the whole group
Comment by Niko Humalamäki (aparaatti) - Saturday, 12 July 2014, 19:03 GMT
I have the same error from eric and from python cli. Is that "_ZTI11QsciPrinter" some kind of build specific hash, which maybe should be changed in PyQt4 -package?

erics error message:
.
.
.
from PyQt4.Qsci import QSCINTILLA_VERSION_STR
ImportError: /usr/lib/python3.4/site-packages/PyQt4/Qsci.so: undefined symbol: _ZTI11QsciPrinter


Ok, I rebuilt pyqt4 from ABS and it didn't help.
Comment by Niko Humalamäki (aparaatti) - Sunday, 13 July 2014, 06:35 GMT
Now I built qscintilla again from abs and installed all the created packages and now eric started ok and import in python cli works.

So I built pyqt4 first installed all created packages and then built qscintilla and installed all created packages.
Comment by prash (prash) - Monday, 14 July 2014, 22:05 GMT
I came across this bug when the latest version of Tortoise HG wouldn't run. Their recommendation of recompiling and reinstalling qscintilla (all 4 packages on Arch) worked for me. Incidentally, the bug reporter was running Arch too. The bug report is at https://bitbucket.org/tortoisehg/thg/issue/3807/bug-report-when-starting-the-application
Comment by Andrea Scarpino (BaSh) - Tuesday, 15 July 2014, 07:08 GMT
I'll rebuild qscintilla packages again then.
Comment by Niko Humalamäki (aparaatti) - Tuesday, 15 July 2014, 11:16 GMT
The bug came back after update... I built qscintilla again and installed rebuilt python-qscintilla-common-2.8.3-2-x86_64.pkg.tar.xz. It didn't help. Then I installed rebuilt python-qscintilla-2.8.3-2-x86_64.pkg.tar.xz, after which bug disappeared. Could there be something machine or architechture depented in qscintilla build...

there is in packaging:
"${pkgdir}"/usr/lib/python3.4/site-packages/PyQt4/Qsci.so

is that Qsci.so somehow corrupt?

edit: The package from ABS wasn't 2.8.3-3, but since the change between 2.8.3-2 and 2.8.3-3 was only incrementing the version number in PKGBUILD the 28.3-2 is the same as 2.8.3-3.
   python-qscintilla-2.8.3-2-x86... (156.6 KiB)
Comment by prash (prash) - Tuesday, 15 July 2014, 11:51 GMT
My experience matches that of @aparaatti. Packages from Arch repositories fail, but my own builds from ABS work as expected.
Comment by Massimiliano Torromeo (mtorromeo) - Tuesday, 15 July 2014, 14:55 GMT
Bug still present in qscintilla-2.8.3-3-x86_64
Comment by kachelaqa (kachelaqa) - Tuesday, 15 July 2014, 17:13 GMT
I can also confirm that the bug is still present in qscintilla-2.8.3-3-x86_64.

Looking at the package change history for pyqt and qscintilla, I wonder whether the root of the problem may be the switch to using the configure-ng.py script in pyqt4 4.11-1. The qscintilla packages were not also rebuilt at the same time (in fact, qscintilla-2.8.2 was skipped altogether), and so the current set of packages are the first to be built in combination with the new configure script. Another possible complicating factor is the addition of the !buildflags option in the qscintilla 2.8.1-2 PKBUILD, which was introduced as a fix for a very similar bug in  FS#39672  (and please note that that issue also has a pending re-open request for the same reasons as this one did).

Loading...