From: Jamie Zawinski <jwz@jwz.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: sharedrepository=group not working
Date: Mon, 3 Dec 2018 21:24:51 -0800 [thread overview]
Message-ID: <903E1F42-3911-471D-B754-7592A5FD2CC7@jwz.org> (raw)
In-Reply-To: <20181204045051.GA23351@sigill.intra.peff.net>
On Dec 3, 2018, at 8:50 PM, Jeff King <peff@peff.net> wrote:
>
> I don't suppose this is leaving those incoming-* directories sitting
> around so we can inspect their permissions (it's suppose to clean them
> up, so I doubt it). If you're up for it, it might be interesting to
> patch Git to inspect the umask and "ls -l" the objects/ directory at the
> problematic moment. The interesting point is when we call into
> tmp-objdir.c:setup_tmp_objdir().
The problem was that Apache was setting my umask to 113! With that:
+ ls -ldF ./objects/incoming-w7agmb/pack objects/incoming-w7agmb
ls: cannot access ./objects/incoming-w7agmb/pack: Permission denied
drw---S--- 2 apache cvs 4096 Dec 3 21:14 objects/incoming-w7agmb/
error: remote unpack failed: unable to create temporary object directory
With 002 it succeeds:
+ ls -ldF ./objects/incoming-IbGS6h/pack objects/incoming-IbGS6h
drwx--S--- 3 apache cvs 4096 Dec 3 21:19 objects/incoming-IbGS6h/
drwxrwsr-x 2 apache cvs 4096 Dec 3 21:19 ./objects/incoming-IbGS6h/pack/
So I fixed my umask and got it working, but maybe a test for "your umask is dumb" is worthwhile.
Thanks for your help!
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
prev parent reply other threads:[~2018-12-04 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 3:27 sharedrepository=group not working Jamie Zawinski
2018-12-04 4:09 ` Jeff King
2018-12-04 4:19 ` Jamie Zawinski
2018-12-04 4:20 ` Jamie Zawinski
2018-12-04 4:50 ` Jeff King
2018-12-04 5:24 ` Jamie Zawinski [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=903E1F42-3911-471D-B754-7592A5FD2CC7@jwz.org \
--to=jwz@jwz.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).