Version bumps for pyqwt, to dev-python/pyqwt-4.2.3 and dev-python/pyqwt-5.1.0. pyqwt-4.2.3 finally gets rid of numeric and numarray dependencies, as it can use numpy only (and it's recommended). pyqwt-5.1.0 is just a bugfix release, that seems to fix bug #247147, at least in my case (I was also affected by the bug, but this version compiles). Ebuilds are coming. A suggestion: both dev-python/pyqwt and x11-libs/qwt are slotted (pyqwt are the python bindings for qwt), but the 4* versions are in slot 0, and the 5* in slot 5. IMHO 4* versions should be in slot 4. Reproducible: Always
Created attachment 173508 [details] dev-python/pyqwt-4.2.3.ebuild The ebuild for the 4.2.3 version, quite different. Note the distcc thing, I don't know how to handle that, even I'm not sure what option must be passed to the configure script. I removed some patches that AFAIK are unneeded now, because they are fixed by using numpy.
Created attachment 173510 [details] dev-python/pyqwt-5.1.0.ebuild Ebuild for 5.1.0 version. Is similar to the one for 5.0.1, but I removed that manual sed-based patchig and used a regular patch, IIRC this kind of things should be avoided.
Created attachment 173515 [details, diff] pyqwt-5.1.0-various-fixes.patch The aforementioned patch. Sorry, I don't have an acronym for this comment.
Hello, Juan, thanks for the ebuilds. But Ive been having issues with pyqwt-4.2.3. It dies with this message: Setup the qwt package build. sip invokation: '/usr/bin/sip -I /usr/share/sip -b tmp-qwt4qt3/qwt4qt3.sbf -c tmp-qwt4qt3 -x Qt_STYLE_WINDOWSXP -x Qt_STYLE_INTERLACE -x Qt_STYLE_WINDOWSXP -x Qt_SIP_PRE_4_7_2 -x VendorID -t WS_X11 -t Qt_3_3_6 -x HAS_NUMARRAY -x HAS_NUMERIC -x HAS_QWT5 ../sip/qwt4qt3/QwtModule.sip' sip: ../sip/qwt4qt3/common/QwtMemArray.sip:35: %MappedType template for this type has already been defined SIP failed to generate the C++ code. with sip-4.7.9 Can you tell me what sip and PyQT versions you used to build this? 4.6 and 3.17? Thanks
Hi, pyqwt-5.1.0 has been bumped. I'm not sure of the utility of keeping a pyqwt-4.2.* which does not seem maintained upstream anymore. Also for 5.1.0, the patch attached here was of no use. Can you confirm these?
*** Bug 283689 has been marked as a duplicate of this bug. ***
I thought would share what I have learned: I renamed the pyqwt 5.1.0 ebuild (and updated the location of the documentation) in portage to 5.2.0 and it compiled fine, however it did not install because of the existing files /usr/lib64/python2.6/site-packages/PyQt4/uic/widget-plugins/qwt.py{c,o} put there already by PyQt4. I read on the riverbankcomputing mailing list ( http://www.mail-archive.com/pyqt@riverbankcomputing.com/msg18383.htm ) that the files put there by PyQt4 are superfluous. I removed the superfluous files ( qwt.py{c,o} ), emerged pyqwt 5.2.0 and everything seems to be working fine. I don't know if there is some way to fix this with the pyqwt ebuild or if this is a problem that should be addressed by the PyQt4 ebuild. Hope this information helps someone.
If that file is really superfluous, then please ask upstream to remove it from the distributed tarball :)
I did as Keith, above, did. Copied the ebuild to /usr/local/portage.. Changed the ebuild name and change the qwt version from 5.1 to 5.2 It compiled and installed fine but not until I had deleted the files Keith mentioned.
Just a quick update: the colliding file is no longer installed by PyQt4-4.6
Created attachment 213141 [details] pyqwt-5.2.0.ebuild Ebuild to pyqwt-5.2.0 with some changes and QA fixes.
As Qt3 is on its way out, only pyqwt-5 will be bumped.
5.2.0 committed. Thanks!
and the credits? :(
You're right, I should've included them. Added.
