This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Maintainer for git?
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 27 Jan 2014 19:11:19 -0500
- Subject: Re: Maintainer for git?
- Authentication-results: sourceware.org; auth=none
- 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>
- Reply-to: cygwin at cygwin dot com
On 1/27/2014 5: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(?)).
Yes, this is what setup*.exe does if the DLL it's trying to replace is
in use. setup*.exe will warn you about such cases and ask if you want
to continue (and have to reboot to complete the installation) or if you
prefer to kill the app using the DLL. You apparently missed that and
ended up with the former option.
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.
FYI, this is not the recommended way to handle this, since it leaves
a scheduled DLL move on reboot in an unpredictable state. So if you
see a DLL with this extension in the future, just reboot.
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.
Right, see above.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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