From: Bill Hoffman <bill.hoffman@kitware.com>
To: cygwin@cygwin.com
Subject: Re: git and openssh issue
Date: Fri, 23 Jul 2010 01:53:00 -0000 [thread overview]
Message-ID: <4C48EE1A.1040705@kitware.com> (raw)
In-Reply-To: <4C48C9B3.60602@bopp.net>
On 7/22/2010 6:44 PM, Jeremy Bopp wrote:
> Just to clarify things, are you hosting your first clone under Cygwin
> (from which you make another clone using Cygwin which fails), or are you
> hosting it under a non-Windows system? It might be good to try this
> under the conditions of Cygwin client<-> Cygwin server, Cygwin client
> <-> non-Windows server, and non-Windows client<-> Cygwin server.
>
We are doing cygwin client to a Linux server that hosts git via ssh.
> Hopefully, we can localize the problem to just the client or server code
> under Cygwin's ssh. The bisect operation is not a bad idea, but I'm not
> sure what revision of the openssh source was last known to work. Given
> that this is still not 100% reproducible even for you (if I understand
> you correctly), the bisect tests may not be completely reliable anyway.
>
It is not that unreproducible... It fails maybe 5 out of 6 tries. If
you can get it to work 10 out of 10 times then I would say you don't
have the problem.
According to this thread:
http://git.661346.n2.nabble.com/Error-when-cloning-gc-ed-repository-td4425832.html
> I downgraded just the openssh package in cygwin from 5.5p1-1 to
5.4p1-1 and the
> problem went away. This was easier than switching to putty/plink.
It seems that openssh 5.4p1-1 worked. So, that would be a good place to
start.
> BTW, are you using text mode mounts under Cygwin for any of these
> repository clones?
>
No, it is all binary mode mounts under Cygwin.
> I'm going to try to make some time this evening to give this a quick test.
>
Sounds good, thanks!
-Bill
--
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
next prev parent reply other threads:[~2010-07-23 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 17:15 Bill Hoffman
2010-07-21 5:48 ` Jeremy Bopp
2010-07-22 15:22 ` Bill Hoffman
2010-07-22 15:49 ` Jeremy Bopp
2010-07-22 19:49 ` Bill Hoffman
2010-07-22 23:48 ` Jeremy Bopp
2010-07-23 1:53 ` Bill Hoffman [this message]
2010-07-23 16:28 ` Jeremy Bopp
2010-07-23 17:01 ` git and openssh issue (eblake?) Christopher Faylor
2010-08-02 14:08 ` Bill Hoffman
2010-08-12 13:46 ` Bill Hoffman
2010-10-03 2:54 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C48EE1A.1040705@kitware.com \
--to=bill.hoffman@kitware.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).