DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=ih
	bj+clKo0z4iU3+gxePajh9DZVwQ0wNhkjbMsI8ikzFX/CnObBmHgl2k+Ui39LvMF
	s9+cz8U2oLde2W6ss3HdlC6c4yuCvmrX0yeZUxZKI1P/sA2WpgWTCvpCgzf6ijJi
	kIBlkvLsoH/jc/yAzmhs5NP1NsCk/Dt9NZGiA/eRc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <CALgEz7qU0qbp+EOHTQfQEX_gNxEi3Nkz2Ge41CG1iZY95HvmCQ@mail.gmail.com>
References: <CA+kUOakGhMYEP5kjmLk1HeWTi9QNTp1Fnk5YF3JuqR_fUc6hPg AT mail DOT gmail DOT com>	<20140115105534 DOT GB31912 AT tastycake DOT net>	<CAAXzdLX0YQTBVOkjUq3f-Jr03Cx5PzsY3_gRYO9rpp_GXOQKYw AT mail DOT gmail DOT com>	<CALgEz7qhf85-kdBCqFWWjni8rw8iTvabtdnBu=z4-tVmy_+jTg AT mail DOT gmail DOT com>	<CAAXzdLXQ-MfUQj6Zh4FSCgGgwwZ82OpkPTWznp5vVFXXeeKvHw AT mail DOT gmail DOT com>	<CALgEz7o7Sm2+NF=Fc3Wpp+Fy=+LQiz0aAc-+Pp+s=-Pjw--AuQ AT mail DOT gmail DOT com>	<CAM7Q9ZvnA4ukDXdbQExX7mje=6yx=0STzQTKAbWhG3jApGHmJw AT mail DOT gmail DOT com>	<20140123105142 DOT GN2357 AT calimero DOT vinschen DOT de>	<20140125115958 DOT GU2357 AT calimero DOT vinschen DOT de>	<CALgEz7pWERwfw=rc_bGPmiUMUrMwBcmpd2kuupsUSG_oxCWspw AT mail DOT gmail DOT com>	<20140126191940 DOT GA645 AT tastycake DOT net>	<CALgEz7qU0qbp+EOHTQfQEX_gNxEi3Nkz2Ge41CG1iZY95HvmCQ AT mail DOT gmail DOT com>
Date: Mon, 27 Jan 2014 14:51:07 -0800
Message-ID: <CALgEz7oyGnJOnMYtojJ_+s+ouaF8ZuGMW5pMVVzY_15phcie6w@mail.gmail.com>
Subject: Re: Maintainer for git?
From: Balaji Venkataraman <balaji DOT s DOT venkataraman AT gmail DOT com>
To: Cygwin <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jan 27, 2014 at 2:30 PM, Balaji Venkataraman wrote:
> On Sun, Jan 26, 2014 at 11:19 AM, Adam Dinwoodie wrote:
>
>> I was previously managing to reproduce this, but since updating to
>> Corinna's latest OpenSSL builds, I've not had any issues.  Is it
>> possibly an out-of-date library hanging around in memory?  Have you
>> tried restarting all your Cygwin processes and/or rebooting your system?
>> I'm surprised Corinna's changes would fix it for me but not for you.
>
> Based on the above, I went back and checked if the openssl update was
> all good. Not quite. Apparently, since I had sshd running when I
> updated the openssl package, looks like the cygcrypto-1.0.0.dll was
> not properly replaced. I ended up w/ a .new file (created by
> setup.exe(?)). I killed sshd renamed the .dll and reran the clone. It
> seems to work (see below) except for one error but I do have a clone
> now. It might be a good idea to perhaps print some warning messages
> when updating packages whose dlls are in use - unless that is already
> happening and I have missed them. But overall, the fix seems to do the
> trick. Thanks again to all.
>
> x86$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> linux
> Cloning into 'linux'...
> remote: Counting objects: 3408476, done.
> remote: Compressing objects: 100% (517865/517865), done.
> Receiving objects: 100% (3408476/3408476), 712.95 MiB | 460.00 KiB/s, done.
> remote: Total 3408476 (delta 2869731), reused 3400091 (delta 2861452)
> Resolving deltas: 100% (2869731/2869731), done.
> Checking connectivity... done.
> error: git-remote-https died of signal 13
> Checking out files: 100% (45625/45625), done.

I did a very quick search on the git-remote-https error and I found a
recent thread[1]. Hoping someone can track it down on Cygwin too.
FWIW, I don't have curl installed - just libcurl.

cygcheck -f /usr/bin/*curl*
libcurl4-7.34.0-1

[1] http://git.661346.n2.nabble.com/error-git-remote-https-died-of-signal-13-td7599771.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple