Re: 'error: unable to set permission to './objects/...'
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Nov 23, 2009, 09:52 UTC
- Message-ID
- <46a038f90911230152j34f42e85ibf4ed57660bd2cf2@mail.gmail.com>
- In-Reply-To
- <7vd43acf7y.fsf@alter.siamese.dyndns.org>
On Mon, Nov 23, 2009 at 12:27 AM, Junio C Hamano <gitster@pobox.com> wrote:
> And the chmod() fails > in this codepath. Then what? Wouldn't it make the resulting repository > unusable?
Slightly off-topic: I keep encountering hosts where core.sharedrepository doesn't always work with git+ssh. It may be related to old git versions (I see 1.5.8 in a host where I've seen it happen recently), but I never fails to baffle me.
Been sysadmin'ing and developing on linux since '98 and there is nothing to prevent git from chmod'ing things right. And I know a few things about git's plumbing :-) -- don't think it should be mysteriously failing.
(And in several git repo servers I've spotted a cronjob doing chmod -R g+rwx, applied by sysadmins to make the devs STFU about it ;-) ).
Is there a shortlist somewhere of reasons for it to be ignored? Perhaps it is a known bug in old versions? -- the repo servers are often behind...
Puzzled minds want to know.
m
-- martin.langhoff@gmail.com martin@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff