Closed ghost closed 12 years ago
This would appear to be a problem with your gitolite installation. You need to fully install gitolite first. Use the instructions for gitolite install that comes with that package. At the top of the README file for this plugin, there is instruction about what to do with the public/private key pair that you have generated for interfacing between gitolite and Redmine. I suggest that you follow the README very carefully.
Sorry for closing this prematurely -- I have it marked as a configuration problem for now.
How is it going?
Are you still around? If I don't hear from you, I'll assume that you fixed your problem...
John,
I am so very sorry for leaving you hanging on this; I got so busy this week I became very disorganized.
You probably did fix the problem, but I will still check now that my week is over
On Wed, Apr 4, 2012 at 6:56 PM, John Kubiatowicz < reply@reply.github.com
wrote:
Are you still around? If I don't hear from you, I'll assume that you fixed your problem...
Reply to this email directly or view it on GitHub:
https://github.com/kubitron/redmine_git_hosting/issues/38#issuecomment-4965050
The latest commits did not fix the issue. However, I'm going with your previous concept of gitolite not being setup correctly - but I think it is prior to gitolite even being invoked so it must be something with my linux environment. I'll try to track this external issue down and post my findings here.
Did you ever run "gl-setup" manually with your key? You need to do that to get gitolite setup. If you notice, there is an error message above from gl-setup that says "looks like first run". Just because gitolite is installed already by your installation does mean that it has been set up. Get the instructions for gitolite installation off the web and notice that you need to:
Make sure that these keys have the right permissions as indicated in the readme....
Hello. Please pull the latest version of the repository and look at the README (or look at it online). I've put in explicit instructions on how to configure gitolite and generate the repository key. In particular, there are new instructions in #1 and #4 of the "Step by step configuration instructions". Perhaps this will help?
Did you ever get this working??? If I don't hear from you soon, I'll close out this bug report.
Sorry this took so long, you can close this, I reinstalled a new installation of ubuntu, all of my dependencies, followed your guide and it worked. I must have just destroyed my environment on the old VM because I just could not fix it. Regardless, it was my environment so not a bug here.
Great!
Glad to hear it is working. Let me know if you have other problems.
Any interaction I had with git, I was having a difficult time. The log produced something like below for one example. When I would copy the commands and run them as my git user, no problems were reported. When redmine would run it, it looked like the home directory was not being prepended to the relative git paths.
I simply set the home environment variable in init.rb and everything started working great. I don't know why redmine would not have access to the home environment variable, but setting it manually makes everything work.
I have this version of redmine checked out, which is 1.3.2+ c17e7e8
I have this version of kubitron redmine_git_hosting, from about 3/28/2012 fef6fda
I'm running Ubuntu Wheezy, testing. All of the latest binary packages provided by the distribution as well as gems. In other words the only source packages on my machine are redmine and it's plugins.
You can actually see where "~/" is getting translated to "" in the log below
_*> Command failed (return 2): cat /var/www/redmine-dev/vendor/plugins/redmine_git_hosting/contrib/hooks/post-receive.redmine_gitolite.rb | /var/www/redmine-dev/vendor/plugins/redmine_git_hosting/bin/run_as_git_user 'cat - > ~/.gitolite/hooks/common/post-receive' _*> sh: 1: cannot create ./.gitolite/hooks/common/post-receive: Directory nonexistent
Log output: