git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dilip M" <dilipm79@gmail.com>
To: "Brian Foster" <brian.foster@innova-card.com>
Cc: "Reece Dunn" <msclrhd@googlemail.com>, "git list" <git@vger.kernel.org>
Subject: Re: gitk doesn't work w/o sudo.
Date: Tue, 20 Jan 2009 22:21:09 +0530	[thread overview]
Message-ID: <c94f8e120901200851n21c6d67r3c43e3efd435e3db@mail.gmail.com> (raw)
In-Reply-To: <200901200912.14432.brian.foster@innova-card.com>

On Tue, Jan 20, 2009 at 1:42 PM, Brian Foster
<brian.foster@innova-card.com> wrote:
> On Monday 19 January 2009 15:37:06 Dilip M wrote:
>> On Mon, Jan 19, 2009 at 5:29 PM, Reece Dunn <msclrhd@googlemail.com> wrote:
>> > 2009/1/19 Dilip M <dilipm79@gmail.com>:
>> >> ..I recently install GIT on Ubuntu (hardy) box....I am able to use
>> >> 'gitk' only If I do 'sudo'. Without 'sudo' it complains 'repository
>> >> not found'
>> >
>> > Who is the owner of the repository directory (and the .git directory)
>> > and what are the permissions on the directory?  [ ... ]
>>
>> dm-laptop:~/repos/atria> id -a
>> uid=1000(dm) gid=1000(dm)  [ ... ]
>> dm-laptop:~/repos/atria> ls -lh .git/
>>[... all looks Ok ...]
>
>  repeating Reece's question, what is the permissions/owner
>  _of_the_directory_which_contains_ the '.git/' directory?
>  I can reproduce this behaviour (git 1.6.0.4) simply by
>  denying myself search (née execute) permission on that
>  directory, for entirely obvious reasons.

It's the same issue....Any ENV variable I can set to debug this...?

dm-laptop:~/repos/atria> id -a
uid=1000(dm) gid=1000(dm)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),107(fuse),109(lpadmin),115(admin),1000(dm)

dm-laptop:~/repos/atria> ls -ld .git
drwxr-xr-x 8 dm dm 4096 2009-01-19 22:34 .git

dm-laptop:~/repos/atria> ls -la .git
total 68
drwxr-xr-x 8 dm dm 4096 2009-01-19 22:34 .
drwxr-xr-x 6 dm dm 4096 2009-01-18 23:28 ..
drwxr-xr-x 2 dm dm 4096 2009-01-18 23:24 branches
-rw-r--r-- 1 dm dm   20 2009-01-19 22:28 COMMIT_EDITMSG
-rw-r--r-- 1 dm dm  256 2009-01-18 23:28 config
-rw-r--r-- 1 dm dm   58 2009-01-18 23:24 description
-rw-r--r-- 1 dm dm   89 2009-01-19 20:15 FETCH_HEAD
-rw-r--r-- 1 dm dm   23 2009-01-19 21:49 HEAD
drwxr-xr-x 2 dm dm 4096 2009-01-18 23:24 hooks
-rw-r--r-- 1 dm dm 5280 2009-01-19 22:28 index
drwxr-xr-x 2 dm dm 4096 2009-01-19 22:34 info
drwxr-xr-x 3 dm dm 4096 2009-01-19 22:34 logs
drwxr-xr-x 4 dm dm 4096 2009-01-19 22:34 objects
-rw-r--r-- 1 dm dm   41 2009-01-19 20:15 ORIG_HEAD
-rw-r--r-- 1 dm dm  153 2009-01-19 22:34 packed-refs
drwxr-xr-x 5 dm dm 4096 2009-01-18 23:28 refs

dm-laptop:~/repos/atria> umask
22


-- DM

  reply	other threads:[~2009-01-20 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 10:16 gitk doesn't work w/o sudo Dilip M
2009-01-19 11:59 ` Reece Dunn
2009-01-19 14:37   ` Dilip M
2009-01-20  8:12     ` Brian Foster
2009-01-20 16:51       ` Dilip M [this message]
2009-01-20 17:10         ` Matthieu Moy
2009-01-20 17:35           ` Dilip M
2009-01-20 18:00             ` Reece Dunn
2009-01-20 17:16         ` Johannes Schindelin
2009-01-20 18:20           ` Dilip M
2009-01-20 21:10             ` Johannes Schindelin
2009-01-19 14:48 ` Jing Xue
2009-01-19 15:35   ` Dilip M

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=c94f8e120901200851n21c6d67r3c43e3efd435e3db@mail.gmail.com \
    --to=dilipm79@gmail.com \
    --cc=brian.foster@innova-card.com \
    --cc=git@vger.kernel.org \
    --cc=msclrhd@googlemail.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 NNTP newsgroup(s).