X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.0 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<28163005.post@talk.nabble.com>
Date:	Wed, 7 Apr 2010 03:12:35 -0700 (PDT)
From:	nothize <nothize AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: git stopped working with 1.7.1
In-Reply-To:	<26824.1268333412@gemini.franz.com>
MIME-Version:	1.0
References:	<10711 DOT 1261594527 AT gemini DOT franz DOT com> <27300928 DOT post AT talk DOT nabble DOT com> <4B5D7DDF DOT 6070904 AT gmx DOT de> <6ee4c8381002121948x2a0a48fci7918eae743cc03c8 AT mail DOT gmail DOT com> <26824 DOT 1268333412 AT gemini DOT franz DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hi Brian,

I had the same issue, lets see if my cause is your cause too.

After I've replaced(or removed!) %windir%\system32\cygz.dll with the newer
one in Cygwin, git 1.7.0.4 worked well. Perhaps I've manually copied an
older cygz.dll to there sometimes ago.....I can't remember.

Some sub-commands of git like git-upload-pack tries to load a
wrong/conflicting version of dll from somewhere.

Note that I have the registry value to allow "loading DLL from the same
directory preceding the path" but %windir%\system32 is always the first in
the PATH environment variable.

HTH

Nothize


Kevin Layer wrote:
> 
> Brian L. <brian AT blucz DOT com> wrote:
> 
>>> From this thread I gather that little or no progress has been made on
>>> addressing the root cause of this issue. It still seems to be broken
>>> with the latest 1.7 series packages.
>>> 
>>> What is the proper method for getting this bug in front of the guys
>>> who maintain the openssh package? The cygwin website suggests that the
>>> mailing list is the proper channel, but it doesn't seem like anyone's
>>> seriously looking into this as an openssh issue.
>>> 
>>> It's clearly affecting more than a few users and the workaround, while
>>> reliable, is quite lame. Can this please get a little bit more
>>> priority?
> 
> and another month goes by...
> 
> If there is work going on behind the scenes, it would be nice to hear
> from the developer(s) working on it.
> 
> If it is not being worked on... I agree with Brian.  This is a serious
> impediment to using Cygwin 1.7.  I would think it would be of top
> priority.
> 
> Thanks.
> 
> Kevin
> 
> --
> 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
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/git-stopped-working-with-1.7.1-tp26905956p28163005.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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

- Raw text -