On Sun, Nov 14, 2010 at 03:17:16PM +, Simon McVittie wrote:
> On Sun, 14 Nov 2010 at 12:51:34 +0100, Daniel Stenberg wrote:
> > This turned out to be a minor bug in curl, yes, and I've fixed it
> > upstream now.
>
> Thanks!
>
> (https://github.com/bagder/curl/commit/cbf4961bf3e42d88f6489f981e
On Sun, 14 Nov 2010 at 12:51:34 +0100, Daniel Stenberg wrote:
> This turned out to be a minor bug in curl, yes, and I've fixed it
> upstream now.
Thanks!
(https://github.com/bagder/curl/commit/cbf4961bf3e42d88f6489f981efd509faa86f501
for those following the Debian bug log)
> BUT, I'd like to str
On Sat, 13 Nov 2010, Simon McVittie wrote:
# GNUTLS backend, zero timeout, fails ./debian/build-gnutls/src/curl -k
https://apt-test.aviatis.com/apt-cacher/ftp.us.debian.org/debian/dists/squeeze/Release
--cert ../test-client.apt-test.aviatis.com.crt --key
../test-client.apt-test.aviatis.com.key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(Ramakrishnan, would you mind pushing recent versions of curl to git.debian.org?
The last thing there seems to be 7.20.1-2 with the tag missing.
If you've lost the git history since then, I have a tree of git-import-dsc
imports (plus some random hack
On Sat, 13 Nov 2010, Steve M. Robbins wrote:
Does curl really treat the default value as 0 seconds timeout on the
connection? Or does it treat 0 as unlimited (i.e. no timeout)? The manpage
for curl_easy_setopt is unclear on this.
curl treats a TIMEOUT explicitly set to 0 as a way to disable
Hi,
Reading through this bug report, I understand that the change in
apt-transport-https (not setting CURLOPT_TIMEOUT) broke apt-get.
David Kalnischkies reassigned this to libcur3-gnutls stating that the
default value for this option is 0 and implying that this is a bug.
Does curl really treat t
6 matches
Mail list logo
