From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: git clone fails with: error: chmod on config.lock failed: Invalid argument
Date: Wed, 27 Jan 2016 18:33:00 -0000 [thread overview]
Message-ID: <56A8C67A.6070101@cornell.edu> (raw)
In-Reply-To: <trinity-3a438ac3-41ea-4364-8a55-e9750829ee24-1453898493961@3capp-gmx-bs63>
On 1/27/2016 7:41 AM, Rainer Blome wrote:
> Hi!
>
> When I use "git clone foo bar" on a Linux host, it works as expected.
>
> git clone foo bar
> Cloning into 'bar'...
> done.
>
> When I use the same command on my Cygwin 64 installation, this used
> to work, but does not work any more. I can fetch and otherwise use
> Git in existing repos all right (have not noticed anything else
> amiss), but the clone command fails like this:
>
> ----
> cd /cygdrive/c/base
> git clone foo bar
> Cloning into 'bar'...
> error: chmod on /cygdrive/c/base/bar/.git/config.lock failed: Invalid argument
> error: chmod on /cygdrive/c/base/bar/.git/config.lock failed: Invalid argument
> error: chmod on /cygdrive/c/base/bar/.git/config.lock failed: Invalid argument
> error: chmod on /cygdrive/c/base/bar/.git/config.lock failed: Invalid argument
> error: chmod on /cygdrive/c/base/bar/.git/config.lock failed: Invalid argument
> fatal: 'origin' does not appear to be a git repository
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> ----
>
> Directory `bar` exists neither before nor after the attempted cloning.
> In the parent directory, manually creating a subdirectory works as
> expected:
>
> /cygdrive/c/base> mkdir bar; ls -ld bar; rmdir bar
> drwx------+ 1 username 123 0 Jan 27 13:13 bar
>
> The issue is not restricted to local cloning, the same messages are
> printed when I attempt to clone from a remote host (from which I
> can clone just fine from a Linux client).
>
> Searching the internet for "cygwin git error chmod on config.lock
> failed: Invalid argument" gave not useful results.
>
> I first noticed the issue after having upgraded to Cygwin 2.4.0-1.
> Juding from the directory creation times in `base`,
> it looks like the last successful clone happened on 2015-07-28.
> I do not know which version of Cygwin I used at that time,
> I update roughly once a month.
>
> Today, I upgraded to 2.4.1-1, the issue persists.
>
> I tried downgrading git from 2.7 to 2.6 via the installer.
> The issue persisted, so I rolled forward again, the issue persisted.
>
> How can I troubleshoot this further?
There might be a problem with the default ACL on the directory
/cygdrive/c/base. What does 'getfacl /cygdrive/c/base' show?
Ken
--
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:[~2016-01-27 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:34 Rainer Blome
2016-01-27 18:33 ` Ken Brown [this message]
2016-01-27 18:39 ` Corinna Vinschen
2016-01-28 6:35 ` Christopher Cobb
2016-01-28 14:31 ` Corinna Vinschen
2016-01-28 15:52 ` chmod failed: Invalid argument [was: git clone fails with: error: chmod on config.lock failed: Invalid argument] Corinna Vinschen
2016-01-28 16:06 ` git clone fails with: error: chmod on config.lock failed: Invalid argument Corinna Vinschen
2016-01-28 17:23 ` Aw: " Rainer Blome
2016-01-28 18:56 ` Corinna Vinschen
2016-04-19 7:22 ` git clone fails with error " Tomas Jura
2016-04-19 7:57 ` Tomas Jura
2016-04-19 8:11 ` Corinna Vinschen
2016-04-19 13:30 ` Tomas Jura
2016-04-19 14:04 ` Corinna Vinschen
2016-04-20 14:06 ` Tomas Jura
2016-04-20 14:29 ` Corinna Vinschen
2016-04-21 7:29 ` Tomas Jura
2016-04-21 7:49 ` Corinna Vinschen
2016-01-28 14:33 ` git clone fails with: error: " Andrey Repin
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=56A8C67A.6070101@cornell.edu \
--to=kbrown@cornell.edu \
--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).