From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: git clone fails with: error: chmod on config.lock failed: Invalid argument
Date: Thu, 28 Jan 2016 14:31:00 -0000 [thread overview]
Message-ID: <20160128132310.GA18626@calimero.vinschen.de> (raw)
In-Reply-To: <trinity-55056902-bdcc-4525-897a-716505b2f75b-1453940836750@3capp-mailcom-lxa03>
[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]
Please don't top-post. Thank you.
On Jan 28 01:27, Christopher Cobb wrote:
> > From: "Corinna Vinschen"
> > On Jan 27 08:30, Ken Brown wrote:
> > > 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
> > > >[...]
> > >
> > > There might be a problem with the default ACL on the directory
> > > /cygdrive/c/base. What does 'getfacl /cygdrive/c/base' show?
> >
> > Also, what does the native windows icacls command print for that
> > directory? The setup of the ACL may give us a hint why git apparently
> > fails to create the bar subdir.
> >
> Or maybe chmod is broken, like it is on my machine:
>
> $ touch x
> $ chmod 777 x
> chmod: changing permissions of ‘x’: Invalid argument
Can you please send the icacls output of the current directory and
the icacls out for the file x?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-28 13:23 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
2016-01-27 18:39 ` Corinna Vinschen
2016-01-28 6:35 ` Christopher Cobb
2016-01-28 14:31 ` Corinna Vinschen [this message]
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=20160128132310.GA18626@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).