threads / discuss / 16576

Problems with EGit

Subject: Problems with EGit

## tl;dr

3 messages between Dec 3, 2008 and Dec 3, 2008.

replies: 2people: 2as markdown or json

Bastian Flinspach· Dec 3, 2008, 11:08 UTC · lore

Hi everyone.

I am a newbie in regards to Linux and especially git. I worked with SVN for some time, but mainly as a client. Never the less, i wanted to set up some form of code repository for my workplace and git seems to be a good fit.

So i installed git on our local development server here in our office. I am the only developer at the time, so i can do as i please. :-) The Server is a debian machine, essentially only running a web server (I develop web apps), which webroot directory is also shared via samba with the otherwise all windows network. The first Version of git i got from the apt was an old one and after some struggling, i managed to update it to 1.6.0.3.g9f8f13. I also created my repository and installed EGit in my eclipse 3.4. In Eclipse, i linked to the samba Folder containing the code.

When i try to commit changes via the command line, everything works fine (well, except for me not being able to use my keyboard right for entering the commit message, but thats probably not important because i want to use EGit anyways). Eclipse recognizes the repository and also displays changes i make. When trying to commit, however, i get a permission denied error.

So, this is basically where i am stuck. What can be the problem and what would be a solution? I assume, that i might have something to do with Linux users and privileges, but i am not yet versed enough to identify the problem on my own.

Please keep in mind, that i am a complete beginner with these topics when answering.

I would appreciate your help.

best regards

Bastian Flinspach

Robin Rosenberg· Dec 3, 2008, 19:21 UTC · re: Bastian Flinspach · lore

Re: Problems with EGit

onsdag 03 december 2008 12:08:11 skrev Bastian Flinspach:

Hi Bastian,

Show 11 quoted lines

> When i try to commit changes via the command line, everything works fine 
> (well, except for me not being able to use my keyboard right for 
> entering the commit message, but thats probably not important because i 
> want to use EGit anyways).
> Eclipse recognizes the repository and also displays changes i make. When 
> trying to commit, however, i get a permission denied error.
> 
> So, this is basically where i am stuck. What can be the problem and what 
> would be a solution? I assume, that i might have something to do with 
> Linux users and privileges, but i am not yet versed enough to identify 
> the problem on my own.

If Git does not have permission problems, neither should EGit, I think, In the workspace there is a file called .metadata/.log that you can inspect. See if you can find anything interesting, i.e. a seemingly relevant stack trace or other error message. The file can be quite large so try to cut it down.

> Please keep in mind, that i am a complete beginner with these topics 
> when answering.

We all started at the beginning.

-- robin

Robin Rosenberg· Dec 3, 2008, 19:45 UTC · re: Robin Rosenberg · lore

Re: Problems with EGit

onsdag 03 december 2008 20:21:57 skrev Robin Rosenberg:

Show 20 quoted lines

> onsdag 03 december 2008 12:08:11 skrev Bastian Flinspach:
> 
> Hi Bastian,
> 
> > When i try to commit changes via the command line, everything works fine 
> > (well, except for me not being able to use my keyboard right for 
> > entering the commit message, but thats probably not important because i 
> > want to use EGit anyways).
> > Eclipse recognizes the repository and also displays changes i make. When 
> > trying to commit, however, i get a permission denied error.
> > 
> > So, this is basically where i am stuck. What can be the problem and what 
> > would be a solution? I assume, that i might have something to do with 
> > Linux users and privileges, but i am not yet versed enough to identify 
> > the problem on my own.
> 
> If Git does not have permission problems, neither should EGit, I think, In the
> workspace there is a file called .metadata/.log that you can inspect. See
> if you can find anything interesting, i.e. a seemingly relevant stack trace or
> other error message. The file can be quite large so try to cut it down.

Starting eclipse from a shell, may yield even more information.

-- robin