-
-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiled git is compiled (in Ubuntu / Debian) using GNUTLS instead of OpenSSL #40
Comments
This is something that I would probably support for source builds. If we moved to use the ark cookbook it is pretty straightforward to allow for overrides for environment options. The version that ships with Ubuntu 14.04 built against GNUTLS? So the package installer gets you that correct version? |
Sry, my initial message was a bit weird :) I had to check things again - yes, in Ubuntu 12.04 and 14.04 you will get GNUTLS supported Git - which does not work with every use case. So using git::source worked for me here - as it compiles against OpenSSL by default - but I was wondering if anyone else at some point would like to change that behaviour - have a choice to compile it against GNUTLS. :) You're considering the ark move then? I tend to use it quite much, it's pretty nice... |
I'm writing configuration management scripts and this is affecting me directly because we're using Stash, apparently gnu_tls uses Tlsv1 and the server doesn't like that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741293 What I don't understand is that this was working just fine with the same server on Ubuntu 12 but in a different repo, hmm. |
accidentally closed this... re-opening |
On latest releases on Debian and Ubuntu (14.04 LTS) the Git has been compiled against GNUTLS instead of OpenSSL. It would be a nice feature when doing source install to decide which one you want to compile against for - because there is a difference. If you compile Git from source - it will compile itself (by default) against OpenSSL. Just a thought...
The text was updated successfully, but these errors were encountered: