Looks like p4python doesn’t support OpenSSL 1.1 yet. Try installing
openssl10-devel (you’ll have to uninstall openssl-devel first).

On Wed, Jan 16, 2019 at 11:57 AM Review User
<[email protected]> wrote:

>
> This now downloads and install cleanly! Thanks.
>
> Have problems compiling with p4python though (OpenSSL) to get a perfoce
> repo installed:
>
> Collecting p4python
>   Using cached
> https://files.pythonhosted.org/packages/36/5a/0a1b192cdecd31cb8bc0d0ba39c73ffd84ce823053d0004823a1fdbe1440/p4python-2018.2.1743033.tar.gz
>     Complete output from command python setup.py egg_info:
>     ****************************************************
>     Cannot match OpenSSL Version string 'OpenSSL 1.1.1 FIPS  11 Sep 2018
>     '
>     ****************************************************
>     ***********************************************
>     ** Cannot build P4Python without SSL support **
>     ***********************************************
>     Attempting to load API from ftp.perforce.com
>     Loaded API into /tmp/p4api-2018.2.1740258
>
>     ----------------------------------------
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-install-XCPcLL/p4python/
>
> I'm presuming original poster will find this too. I have done an openssl
> version and it's the correct version. I've also installed openssl-devel &
> python-devel but it flatly refuses to budge any further.
>
> perforce simply mentions
> https://www.perforce.com/perforce/doc.current/user/p4pythonnotes.txt :
>
>       SSL support
>       -----------
>
>       Perforce Server 2012.1 and later supports SSL connections and the
>       C++ API has been compiled with this support. Since 2017.1 SSL support
>       is mandatory, that is, P4Python has to be compiled with valid OpenSSL
>       1.0.2 libraries.
>
>       To specify which SSL library to use, provide the --ssl [librarypath]
>       switch to the build. Without [librarypath] setup will attempt to run
>       "openssl version" to identify the location of the library path for
>       openssl and whether openssl has the appropriate version
>       (currently >= 1.0.0).
>
>       If the build process cannot find appropriate openssl binary in the
>       standard path, or the path pointed to with the --ssl switch, then
>       P4Python will not be built.
>
>
> On Tuesday, January 15, 2019 at 2:20:12 PM UTC, Stephen Gallagher wrote:
>>
>> On Mon, Jan 14, 2019 at 1:40 PM Stephen Gallagher
>> <[email protected]> wrote:
>>
>> > Here's the problem. Someone broke the stable updates policy and pushed
>> > a backwards-incompatible version of requests-oauthlib into Fedora 29's
>> > updates repositories. I'll stick the older version in the reviewboard
>> > module so it should override the default one. I'll get that fixed up
>> > and do a build shortly.
>> >
>> > Also, I'll update to 3.0.11 because somehow I missed that release.
>>
>> This took a little longer than expected, but I've just submitted
>> https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-ed61972699
>> as an update. It should become available in the updates-testing repos
>> for F29 within 24 hours. Thanks for reporting it!
>>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to