By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2012 - trinity-sip-pre_R14.0.0-x86_64-14.1_64_git_3193_1 installs incompatible sip.so
Summary: trinity-sip-pre_R14.0.0-x86_64-14.1_64_git_3193_1 installs incompatible sip.so
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: slackware (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: amd64 Slackware 14
: P5 blocker
Assignee: Darrell
URL:
Depends on:
Blocks:
 
Reported: 2014-03-11 08:46 CDT by Jim
Modified: 2014-03-25 07:47 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jim 2014-03-11 08:46:28 CDT 
Compiling on Slackware64 14.1 with Darrell's Slackware build scripts (from the git source I downloaded on Jan 30):

trinity-sip-pre_R14.0.0-x86_64-14.1_64_git_3193_1 over-writes a few files from Slackware's sip-4.14.2-x86_64-1 package.  One of these is sip.so, and the trinity version has an incompatible API with some of the other Python tools in 14.1.

For example, if I start up an interactive Python shell and type
   
from PyQt4 import QtCore

I'm rewarded with 

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: the sip module implements API v7.0 to v7.1 but the PyQt4.QtCore module requires API v9.1

This is a show stopper, since it breaks other (innocent bystander) Python programs.

I see that there is also a package called 
trinity-sip4-tqt-pre_R14.0.0-x86_64-14.1_64_git_3193_1 with a supserset of the files from the "trinity-sip-pre_R14.0.0..." packages, but with the files installed in /opt/trinity/... and /usr/lib64/python2.7/site-packages/sip4_tqt/ instead of /usr/bin, /usr/include/python2.7 and /usr/lib64/python2.7/site-packages.

Is it possible that the trinity-sip-pre_R14.0.0... package is a hold-over which should have been removed?  (I note that my previous build of trinity, from the beginning of January, only has trinity-sip-pre_R14.0.0-x86_64-14.1_64_git_2961_1 and no trinity-sip4-tqt-pre_R14.0.0... package.

Thoughts?  Thanks.
Comment 1 Darrell 2014-03-11 15:07:23 CDT 
While the problem sounds like a possible build script issue, my build scripts are not official in any way. I also have no idea how to fix this although the bug report was assigned to me.
Comment 2 Jim 2014-03-11 15:42:24 CDT 
(In reply to Darrell from comment #1)
> While the problem sounds like a possible build script issue, my build
> scripts are not official in any way. I also have no idea how to fix this
> although the bug report was assigned to me.

Given that there is the trinity-sip4-tqt package now, I was wondering whether someone would be able to comment on the requirement of the other sip package.

Can someone who uses some other distro comment on whether there should now be two sip packages, or whether the trinity-sip4-tqt one suffices?

Thanks.
Comment 3 Darrell 2014-03-11 15:50:50 CDT 
I did not notice you originally mentioned using a build script set from Jan. 30. I believe since then the Trinity sip package was transformed into the newer sip4-tqt package. If I understand correctly, this package no longer replaces existing sip files and is more or less a Trinity interface to sip.

I updated my online build scripts with the newer sip4-tqt build scripts.
Comment 4 Darrell 2014-03-19 14:17:29 CDT 
Jim, is this report still valid?
Comment 5 Jim 2014-03-19 14:55:10 CDT 
I tried to build trinity yesterday with yesterday's git source and your March 11 build scripts.

It crashed and burned somewhere along the line (tdebase didn't build, and I am left with a mixture of git_3193 and git_3494 packages).

I haven't had a chance to investigate this, but that is on my list of things to do ASAP.  This time I plan to remove all the trinity packages before starting the build, in case there is some effect related to having old packages around.

I'll either update this bug report when I do that, or file another one about the build not completing :-)
Comment 6 Jim 2014-03-25 07:47:29 CDT 
I got through the build this time and now there is no trinity package which clobbers .../python2.7/site-packages/sip.so.

So I guess this can be closed.