[SRU] qtiplot package needs to be rebuilt against new SIP libraries

[Neudrino]

This is a well known bug happening every release. Thus I just copy the previous bug report (#1311721) from Dufay Basile (https://launchpad.net/~basile-dufay14):

/Quote start/

[Impact]
Python scripting isn't working in Trusty (Ubuntu 16.04).

[Test case]
Qtiplot installed version : 0.9.8.9-14.
1) From the menus, choose "Scripting"->"Scripting Language..."
2) Select Python
3) Error: "Failed to export QtiPlot API: Accessing QtiPlot functions or objects from Python code won't work. Probably your version of Qt/SIP/PyQt differs from the one QtiPlot was compiled against."

[Regression Potential]
None, this is a no code change rebuild.

[Other info]
This bug has been previously reported and fixed for
- Saucy, see bug #1243269
- Raring, see bug #1129237
- Trusty, see bug #1311721

It seems to be a compatibility problem.
It looks quite strange that this bug happens every release...
I hope you could fix this easily.

/Quote end/

[Ivan (mcvanili)]

Confirm the same problem on Ubuntu 16.04.1:amd64

Is there any working build?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ivan (mcvanili)]

I have tried to build the package from source, and it worked. However, the built package did not work on a live cd version of the same system (ubuntu 16.04.1amd64), this means that the trouble is not in the binary version, but in some dependencies. Comparing dependencies for the source code and binary packet I have found that it is enough just to additionally install python-qt4 to make python scripting starts to work.

So solution will be
sudo apt-get install python-qt4

IMHO this is not a bug and even not a broken dependence, because qtiplot may still work without python scripting (and many users even do not need it). So, the thread, probably, may be closed.