[Pypgsql-users] Re: Difficulty using pypgsql rpm

[Stanley A. K. <sk...@cp...>]

Sean -

I think you misinterpreted my configuration.  Perhaps I wasn't clear.

I'm running Python 2.1, which if it wasn't provided on the Red Hat 7.2 CD's
(in addition to the Python 1.5.2 that runs the Red Hat config system) I had
downloaded from python.org.

I had installed the pypgsql 2.1 and 2.2 rpms downloaded from ftp.tummy.com.
 I tried both.  They each created a python2.2 site packages directory and I
symlinked pypgsql from there to the python2.1 site packages directory.

Neither worked when I did the diagnostic I described.  That was the error
traceback I provided.

My suspicion is that the options in setup.py somehow cause the pypgsql 2.1
and 2.2 installed under the rpms as supplied on the ftp site to look in the
wrong places for some shared objects they need.

Since the SRPM keeps the source files other than the rpm spec packaged up
in a tar.gz file that the rpm build uses, I'm not sure how to fix the
setup.py inside the tar.gz package to select the proper options for Red
Hat.  Alternatively, could I symlink from where Red Hat puts any library or
include files that need to be accessed by the files installed by the
pypgsql rpm to where pypgsql looks for them?  What files are involved?

I understand from your response what the python2 in the spec file
represents.  

Thanks in advance for your help on the remaining items.


Stan Klein



At 10:23 AM 10/21/2002 -0600, Sean Reifschneider wrote:
>On Mon, Oct 21, 2002 at 07:05:42AM +0000, Stanley A. Klein wrote:
>>BTW, I got pyPgSQL to appear in python2.1/site-packages by a symbolic link
>>from where it installs under the rpm as provided.
>
>You can't just symlink the files from a 1.5.2 build into the 2.1/2.2
>directories and expect it to work.  You'll need to build a version of
>pypgsql for the 2.1 install native.  The .spec file doesn't include any
>mechanism for doing that, but if while you build the RPM you make sure
>that /usr/bin/python points at the appropriate version, I think it'll do
>the right thing for you.
>
>>Also, the rpm dependencies specify python2.  Python 2.1 does not qualify
>>under the dependency as stated.  You may want to specify something like
>>python >= 2.  Likewise, my python2.1 requires that it be invoked as
>>python2.1, not python2.  Is a symbolic link required there?
>
>Note that "python2" is different than "python version 2".  With Red Hat
>7.3, if you remove the stock python (1.5.2), it will break the GUI
>management tools.  Therefore, I named the Python 2.x packages "python2",
>so that they could be installed next to the existing system.
>
>You may want to try picking up the python 2.2 RPMs from www.python.org
>(which are the "python2" packages) and using that instead of packages
>that install as "python".
>
>Those were the packages I built pyPgSQL with and should work.
>
>Sean
>-- 
> I'm one of the leading experts in the field of Data Mimeing.  Unfortunately,
> I'm not allowed to TELL you anything about it.  -- Sean Reifschneider, 1997
>Sean Reifschneider, Inimitably Superfluous <ja...@tu...>
>tummy.com, ltd. - Linux Consulting since 1995.  Qmail, Python, SysAdmin
>
>