*Solved* esniper SSL certificate problem concerning curl

[khippy]

I like using esniper, current version I use is v2.26.0. Out of a sudden I was involved in the SSL certificate problem and the solution I have was based on the information from the Bug-ID 3480530 at the bug tracker at http://esniper.sf.net I'd like to share with you.

It is very simple.

Curl is using openssl as default. Simply change it to use gnutls by adding a line

Code: Select all

CURL_SSL="gnutls"

to your /etc/make.conf and recompile net-misc/curl and esniper afterwards.

esniper is running again.

It doesn't hurt to run revdep-rebuild finally, too.

[Fog_Watch]

I prefer something like the following in /etc/portage/package.use

Code: Select all

=net-misc/curl-7.24.0 gnutls

.
Thanks for this khippy, I'd still be deep inside Google had it not been for your post.

[khippy]

My pleasure!

Thanks for your note and additionial way on how to do it.

[solamour]

Adding "net-misc/curl gnutls" to "/etc/portage/package.use" didn't work for me, possibly because we need to add "gnutls" to CURL_SSL, not USE.

Code: Select all

[ebuild   R    ] net-misc/curl-7.26.0  USE="ipv6 ssl -ares -idn -kerberos -ldap -ssh -static-libs {-test} -threads" CURL_SSL="openssl -axtls -cyassl -gnutls -nss -polarssl" 2,366 kB

Adding CURL_SSL="gnutls" to "/etc/portage/make.conf" did work.
__
sol

[Hu]

Adding "net-misc/curl gnutls" to "/etc/portage/package.use" didn't work for me, possibly because we need to add "gnutls" to CURL_SSL, not USE.

Code: Select all

[ebuild   R    ] net-misc/curl-7.26.0  USE="ipv6 ssl -ares -idn -kerberos -ldap -ssh -static-libs {-test} -threads" CURL_SSL="openssl -axtls -cyassl -gnutls -nss -polarssl" 2,366 kB

Adding CURL_SSL="gnutls" to "/etc/portage/make.conf" did work.

When this thread was written, the advice before you was correct. The situation changed sometime between August 2012 and now.

[solamour]

Then I believe adding CURL_SSL="gnutls" to "/etc/portage/make.conf" is the correct way, because something like "/etc/portage/package.curl_ssl" would look funny, right?
__
sol

[thenextdon13]

(edit to remove extraneous code tag )
Worked for me, after some finagling. Thank you for posting!!!!

First tried just re-emerging curl after adding "CURL_SSL="gnutls" to /etc/portage/make.conf as listed here

Ended up with this error:

Code: Select all

dylan@BigBox ~/esniper/esniper $ sudo emerge curl

 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!
[ebuild  NS    ] sys-devel/automake-1.12.6 [1.4_p6-r1, 1.5-r1, 1.6.3-r1, 1.7.9-r2, 1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.6]
[ebuild   R    ] net-misc/curl-7.29.0-r1  CURL_SSL="gnutls* -openssl*" 

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

net-misc/curl:0

  (net-misc/curl-7.29.0-r1::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (net-misc/curl-7.29.0-r1::gentoo, installed) pulled in by
    net-misc/curl[curl_ssl_gnutls=,curl_ssl_nss=,curl_ssl_openssl=,-curl_ssl_axtls,-curl_ssl_cyassl,-curl_ssl_polarssl] required by (dev-python/pycurl-7.19.0-r1::gentoo, installed)


!!! Enabling --newuse and --update might solve this conflict.
!!! If not, it might help emerge to give a more specific suggestion.

Had to rebuild pycurl with new dependencies first.

Then emerge of curl went off without a hitch.