Hi,
If libssl.so.1.0.0 is in your /usr and not /usr/local, and p4python is compiled
against it, I'd expect it to work. At this point, I don't know what's wrong
and, without having access to the system, couldn't diagnose it well enough.
I'll think about it more, but unfortunately you're in the b
In my linux box i am having below /usr/lib and /usr/lib64
libssl.so.0.9.7a
libssl.so.0.9.8e
but after my openssl build i only got libssl.so.1.0.0 and it got placed in
/usr/local/lib64/ i do not see any libssl.so in /usr/local/lib so I am not
sure which one Apache is referring
Are there any
In that case, do you then have both OpenSSL 1.0.0 and 1.0.1 on the same system?
It could be that, when run from Apache, the version in /usr/local isn't being
used. You should try backing up the one in /usr/lib and /usr/lib/64, then
symlinking to the new ones.
Christian
--
Christian Hammond -
As i said since my machine was not having openssl1.0.1 installed, hence we
need to build openssl first from source which gets installed at /usr/local/
where these libssl.so gets placed at /usr/local/lib64 and its link also
gets created with the name libcrypto.so.1.0.0, libssl.so.1.0.0
I resta
These e-mails keep ending up directed to me. Let's be sure they're all on the
mailing list.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Apr 9, 2013, at 12:05 AM, Christian Hammond wrote:
> Sorry,
Sorry for multiple mails but i have no option to fetch help from you expect.
How to make review board point to new P4API.so
I have noticed that after p4python build it generates library
libssl.so.1.0.0, I googled it and could not found any relevant answer but i
guess that's the expected behavi
All the P4 files present at /usr/local/lib/python2.7/site-packages
On Tuesday, April 9, 2013 11:11:39 AM UTC+5:30, Christian Hammond wrote:
>
> Yeah, it's possible it's grabbing that one instead.
>
> If p4python is successfully built using OpenSSL, the only thing I can
> think of to cause that er
Yeah, it's possible it's grabbing that one instead.
If p4python is successfully built using OpenSSL, the only thing I can think of
to cause that error would be Review Board using an older copy somehow.
Where's the new P4.* files?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Boa
Here are some more information:
I can see there was old P4Python-2008.2-py2.7.egg-info file present at
site-packages folder, But i had make sure this version's P4.py, P4.pyc,
P4.pyo, P4API.so are moved to some safe place. Will this file make any
difference.
cat easy-install.pth
import sys; sy
Hi Chris,
Reviewboard is using the same version of python for which i have provided
example as below
[GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import P4
There are no Two version of p4python installed, how do i fi
Is Review Board using the same version of Python? Any chance there are now two
copies of p4python installed?
Christian
On Apr 8, 2013, at 4:01, chuck j wrote:
> Dear All,
>
> This is very critical, I am still not able to add SSL enabled perforce
> repository to reviewboard, Please help me.
11 matches
Mail list logo
