git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Paul Umbers <paul.umbers@gmail.com>,
	git@vger.kernel.org, Junio C Hamano <junkio@cox.net>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Git Cygwin - unable to create any repository - help!
Date: Thu, 17 Jan 2008 13:53:44 -0500	[thread overview]
Message-ID: <478FA438.9010909@gmail.com> (raw)
In-Reply-To: <20080116234527.GA3499@steel.home>

Alex Riesen wrote:
> Paul Umbers, Wed, Jan 16, 2008 22:44:10 +0100:
>> Here's the log from the latest strace.
> 
> Something is fishy here (aside from the horrible selection of
> information in the trace output):
> 

That is a matter of opinion. Besides, Cygwin's strace was designed first and
foremost with debugging the Cygwin dll in mind. Perhaps the choice of name for
the utility was a poor one, since it implies that it ought to be the same as
the official strace.

As for the matter at hand:

First, *you must* make sure you inspect every directory in your PATH for other
copies of cygwin1.dll. Sometimes, without telling you, other software packages
will distribute the cygwin1.dll. Often times this is an older version of that
dll. If there are any these found outside of the Cygwin installation tree, you
must remove them from your PATH.

Secondly, reinstalling Cygwin by rerunning setup is not enough. Cygwin is
pretty self-contained and non-invasive (contrary to the popular FUD spread by
MinGWists), but it does have 2 Registry keys which should be axed if you want a
clean install. They are:

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions

Lastly, has the user actually tried reporting this problem to
"cygwin@cygwin.com"? That is the proper list for reporting problems with
official cygwin packaged applications. Both the maintainer of the "git" Cygwin
package and the core Cygwin developers monitor that list, so you are much more
likely to get a solution to your problem there. Nevertheless, it does seem that
in this case it might be a problem with git's handling of failures to create
hard links. But do keep this in mind for future reference.

Cheers,
Nicholas

  parent reply	other threads:[~2008-01-17 19:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 17:21 Git Cygwin - unable to create any repository - help! Paul Umbers
2008-01-14 20:29 ` Alex Riesen
2008-01-14 22:21   ` Paul Umbers
2008-01-15  5:48     ` Alex Riesen
2008-01-15 15:21       ` Paul Umbers
2008-01-15 20:04         ` Alex Riesen
2008-01-15 20:12           ` Paul Umbers
2008-01-15 21:20             ` Alex Riesen
2008-01-15 21:57               ` Paul Umbers
2008-01-15 22:51                 ` Alex Riesen
2008-01-15 21:59               ` Paul Umbers
2008-01-15 22:55                 ` Alex Riesen
2008-01-15 23:02             ` Robin Rosenberg
2008-01-16  7:18               ` Alex Riesen
2008-01-16 15:42                 ` Paul Umbers
2008-01-16 17:55                   ` Junio C Hamano
2008-01-16 18:10                     ` Paul Umbers
2008-01-16 18:38                       ` Alex Riesen
2008-01-16 18:57                         ` Paul Umbers
2008-01-16 18:31                   ` Alex Riesen
2008-01-16 18:48                     ` Paul Umbers
2008-01-16 19:12                       ` Alex Riesen
2008-01-16 19:17                       ` Alex Riesen
2008-01-16 21:44                         ` Paul Umbers
2008-01-16 23:45                           ` Alex Riesen
2008-01-17 18:37                             ` Paul Umbers
2008-01-17 18:51                               ` Linus Torvalds
2008-01-17 19:17                                 ` Johannes Schindelin
2008-01-17 20:13                                 ` Paul Umbers
2008-01-17 20:24                                   ` Linus Torvalds
2008-01-17 20:38                                     ` Pascal Obry
2008-01-17 20:50                                       ` Johannes Schindelin
2008-01-17 20:53                                         ` Pascal Obry
2008-01-17 22:32                                     ` Paul Umbers
2008-01-17 20:18                               ` Alex Riesen
2008-01-17 18:53                             ` Nicholas Wourms [this message]
2008-01-17 20:30                               ` Alex Riesen
2008-01-16 18:50                     ` Paul Umbers
2008-01-15 17:08     ` Pascal Obry

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=478FA438.9010909@gmail.com \
    --to=nwourms@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=paul.umbers@gmail.com \
    --cc=raa.lkml@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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 NNTP newsgroup(s).