On dom, apr 06, 2014 at 07:29:27 +0200, Andreas Metzler wrote:
On 2014-03-13 Alessandro Ghedini gh...@debian.org wrote:
On gio, mar 13, 2014 at 01:31:11 -0400, James Cloos wrote:
[...]
No, I mean the more recent relicense to LGPL3+ OR GPL2+, as mentioned on
the gnutls thread on
On 2014-03-13 Alessandro Ghedini gh...@debian.org wrote:
On gio, mar 13, 2014 at 01:31:11 -0400, James Cloos wrote:
[...]
No, I mean the more recent relicense to LGPL3+ OR GPL2+, as mentioned on
the gnutls thread on debian-devel.
I confirmed it in the README in their HG repo
On mer, mar 12, 2014 at 05:31:22 -0400, James Cloos wrote:
AG == Alessandro Ghedini gh...@debian.org writes:
AG If you are using Debian sid, gnutls-cli is built against libgnutls28
(while
AG licurl uses libgnutls26) so this isn't much useful (unfortunately we can't
AG switch to
AG == Alessandro Ghedini gh...@debian.org writes:
AG If you mean its relicensing to LGPL3+,
No, I mean the more recent relicense to LGPL3+ OR GPL2+, as mentioned on
the gnutls thread on debian-devel.
I confirmed it in the README in their HG repo https://gmplib.org/repo/gmp/
and the changset:
On gio, mar 13, 2014 at 01:31:11 -0400, James Cloos wrote:
AG == Alessandro Ghedini gh...@debian.org writes:
AG If you mean its relicensing to LGPL3+,
No, I mean the more recent relicense to LGPL3+ OR GPL2+, as mentioned on
the gnutls thread on debian-devel.
I confirmed it in the
On Tue, Mar 11, 2014 at 11:27:24PM +0100, Alessandro Ghedini wrote:
So, the problem is not gnutls (or not *just* gnutls), but the fact that the
server doesn't seem to support TLSv1,
That is likely related to this Apache config setting:
# Work around SSL negotiation failed: SSL error: parse
On Tue, Mar 11, 2014 at 11:27:24PM +0100, Alessandro Ghedini wrote:
Now, why does libcurl fails while gnutls-cli (built against libgnutls26) does
not (not by default, anyway)? That may be a bug in libcurl, I'll look into
this
later.
Unfortunately apache2.4 with the SSLProtocol -all +SSLv3
AG == Alessandro Ghedini gh...@debian.org writes:
AG If you are using Debian sid, gnutls-cli is built against libgnutls28 (while
AG licurl uses libgnutls26) so this isn't much useful (unfortunately we can't
AG switch to libgnutls28 for licensing problems).
Didn’t the gmp relicensing fix such
On lun, mar 10, 2014 at 09:47:46 +0100, Andras Korn wrote:
Package: libcurl3-gnutls
Version: 7.35.0-1
Severity: normal
Hi,
this appears to be a regression.
With 7.33.0-1 I could access git repositories over https; with 7.35.0-1 I
can't:
% GIT_CURL_VERBOSE=1 git clone
On Tue, Mar 11, 2014 at 05:48:35PM +0100, Alessandro Ghedini wrote:
Hi,
fatal: unable to access 'https://https.server/repo.git/':
gnutls_handshake() failed: A record packet with illegal version was
received.
Could this repository be made available for testing?
URL sent via private
On mar, mar 11, 2014 at 09:40:05 +0100, Andras Korn wrote:
On Tue, Mar 11, 2014 at 05:48:35PM +0100, Alessandro Ghedini wrote:
If you are using Debian sid, gnutls-cli is built against libgnutls28 (while
licurl uses libgnutls26) so this isn't much useful (unfortunately we can't
switch to
Package: libcurl3-gnutls
Version: 7.35.0-1
Severity: normal
Hi,
this appears to be a regression.
With 7.33.0-1 I could access git repositories over https; with 7.35.0-1 I
can't:
% GIT_CURL_VERBOSE=1 git clone https://https.server/repo.git/
Cloning into 'repo'...
* Couldn't find host
12 matches
Mail list logo
