From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Trouble with Git 2.1.x pushing to repos over Samba
Date: Thu, 30 Apr 2015 10:56:00 -0000 [thread overview]
Message-ID: <20150430105644.GM3657@calimero.vinschen.de> (raw)
In-Reply-To: <397346277.275101.1430383452664.JavaMail.zimbra@ceos.com.au>
[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]
Hi John,
On Apr 30 18:44, John Orr wrote:
> > From: "Michael Enright"
> > $ git push origin master
> > fatal: '//host/path/to/repo.git/' does not appear to be a git repository
> > fatal: Could not read from remote repository.
> [...]
> #: john@johndesktop:/cygdrive/l ; ls -ld .git/objects/
> drwxr-xr-x 1 john Unix_Group+1000 0 Nov 13 14:13 .git/objects/
>
> (albeit, Corinna, with my group issue still not yet resolved)
You tried the /etc/group tweak as I suggested in my latest mail in that
thread, I take it?
> access(/cygdrive/l/.git, R_OK) returned 0
> access(/cygdrive/l/.git, W_OK) returned 0
> access(/cygdrive/l/.git, X_OK) returned -1
>
> The last test is the one run by git, that makes it reject my /cygdrive/l/.git directory.
>
> Not sure if that's relevant, but just in case.
Thanks for the info. I found a really dumb bug in my code. The
access() function is using a Windows function for access checking under
the hood. To account for the Samba account mapping in Cygwin, there's
a function converting the S-1-22-x-y SIDs in the file's ACL to Windows
SIDs if there *is* a mapping. But I made a small mistake which has
a big result: The ACL is not completly copied over, thus the Windows
function has to deal with an incomplete ACL.
I fixed that in the git repo and uploaded new snapshots to
https://cygwin.com/snapshots/ Please give them a try. Don't use the
snapshots for anything else for the time being!
PLEASE TEST ASAP AND REPORT BACK!
I'll be unavailable for a few weeks starting tomorrow, so I'd like to
do a bugfix Cygwin release, preferredly today, if this patch works as
desired.
Thanks,
Corinna
P.S.: As a side-note: While this patch (hopefully) reverts this code to
work as pre-1.7.34, it seems that the internal Windows access
check function is not quite up to the task for Samba shares in
scenarios as John's one. It will always report back the access of
the "others" part of POSIX permission bits. Only with the new
mapping of S-1-22-x-y SIDs to real WIndows accounts, or with
winbindd-supported mapping, the Windows access check will really
work as desired.
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-30 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 4:26 Michael Enright
2015-04-30 8:44 ` John Orr
2015-04-30 8:54 ` John Orr
2015-04-30 10:56 ` Corinna Vinschen [this message]
2015-04-30 11:11 ` Michael Enright
2015-04-30 11:17 ` Corinna Vinschen
2015-04-30 15:02 ` Michael Enright
2015-04-30 15:10 ` Corinna Vinschen
2015-04-30 23:54 ` John Orr
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=20150430105644.GM3657@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).