| View previous topic :: View next topic |
| Author |
Message |
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
 Posted: Sat Jan 26, 2013 9:15 pm Post subject: Installing gitlabHQ fail on `emerge --config "=www-apps |
 |
|
Hello,
I'm trying to setup gitlabHQ on a Gentoo server following the steps given on the CVUT overlay page, but I'm failing on the following step.
It's been a long time I haven't work on gentoo so I'm a bit rusty.
| Quote: | emerge --config "=www-apps/gitlabhq-4.0.0-r2"
Configuring pkg...
* Checking configuration files
chmod: cannot access ‘/var/lib/gitolite/repositories//.gitolite’: No such file or directory
* ERROR: www-apps/gitlabhq-4.0.0-r2 failed (config phase):
* failed to change permissions on /var/lib/gitolite/repositories//.gitolite
*
* Call stack:
* ebuild.sh, line 93: Called pkg_config
* environment, line 4732: Called die
* The specific snippet of code:
* chmod 750 "${repos_path}"/.gitolite || die "failed to change permissions on ${repos_path}/.gitolite";
*
* If you need support, post the output of `emerge --info '=www-apps/gitlabhq-4.0.0-r2'`,
* the complete build log and the output of `emerge -pqv '=www-apps/gitlabhq-4.0.0-r2'`.
* This ebuild is from an overlay named 'cvut': '/var/db/pkg/'
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
* The complete build log is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2/temp/environment'.
* Working directory: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2'
* S: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2/work/gitlabhq-4.0.0' |
When I check the directory /var/lib/gitolite/repositories//.gitolite didn't exists. However a directory with this name existed in the parent folder : /var/lib/gitolite/. I tried create a symlink :
| Code: |
cd /var/lib/gitolite/repositories/
ln -s ../.gitolite ./
|
The command seemed to worked at first, but failed again :
| Quote: |
emerge --config "=www-apps/gitlabhq-4.0.0-r2"
Configuring pkg...
* Checking configuration files
* Copying git hook to /var/lib/gitolite/.gitolite/hooks/
* Initializing database ...
gitlab already exists
fatal: Not a git repository (or any of the parent directories): .git
-- create_table("events", {:force=>true})
-> 0.0799s
-- add_index("events", ["action"], {:name=>"index_events_on_action"})
-> 0.0264s
-- add_index("events", ["author_id"], {:name=>"index_events_on_author_id"})
-> 0.0305s
-- add_index("events", ["created_at"], {:name=>"index_events_on_created_at"})
-> 0.0250s
-- add_index("events", ["project_id"], {:name=>"index_events_on_project_id"})
-> 0.0291s
-- add_index("events", ["target_id"], {:name=>"index_events_on_target_id"})
-> 0.0432s
-- add_index("events", ["target_type"], {:name=>"index_events_on_target_type"})
-> 0.0765s
-- create_table("issues", {:force=>true})
-> 0.0395s
-- add_index("issues", ["assignee_id"], {:name=>"index_issues_on_assignee_id"})
-> 0.0373s
-- add_index("issues", ["author_id"], {:name=>"index_issues_on_author_id"})
-> 0.0681s
-- add_index("issues", ["closed"], {:name=>"index_issues_on_closed"})
-> 0.0319s
-- add_index("issues", ["created_at"], {:name=>"index_issues_on_created_at"})
-> 0.0415s
-- add_index("issues", ["milestone_id"], {:name=>"index_issues_on_milestone_id"})
-> 0.1056s
-- add_index("issues", ["project_id"], {:name=>"index_issues_on_project_id"})
-> 0.0960s
-- add_index("issues", ["title"], {:name=>"index_issues_on_title"})
-> 0.0622s
-- create_table("keys", {:force=>true})
-> 0.0166s
-- add_index("keys", ["identifier"], {:name=>"index_keys_on_identifier"})
-> 0.0403s
-- add_index("keys", ["project_id"], {:name=>"index_keys_on_project_id"})
-> 0.0724s
-- add_index("keys", ["user_id"], {:name=>"index_keys_on_user_id"})
-> 0.0552s
-- create_table("merge_requests", {:force=>true})
-> 0.0232s
-- add_index("merge_requests", ["assignee_id"], {:name=>"index_merge_requests_on_assignee_id"})
-> 0.0548s
-- add_index("merge_requests", ["author_id"], {:name=>"index_merge_requests_on_author_id"})
-> 0.0628s
-- add_index("merge_requests", ["closed"], {:name=>"index_merge_requests_on_closed"})
-> 0.0573s
-- add_index("merge_requests", ["created_at"], {:name=>"index_merge_requests_on_created_at"})
-> 0.0556s
-- add_index("merge_requests", ["milestone_id"], {:name=>"index_merge_requests_on_milestone_id"})
-> 0.0782s
-- add_index("merge_requests", ["project_id"], {:name=>"index_merge_requests_on_project_id"})
-> 0.0711s
-- add_index("merge_requests", ["source_branch"], {:name=>"index_merge_requests_on_source_branch"})
-> 0.0622s
-- add_index("merge_requests", ["target_branch"], {:name=>"index_merge_requests_on_target_branch"})
-> 0.0717s
-- add_index("merge_requests", ["title"], {:name=>"index_merge_requests_on_title"})
-> 0.0787s
-- create_table("milestones", {:force=>true})
-> 0.0321s
-- add_index("milestones", ["due_date"], {:name=>"index_milestones_on_due_date"})
-> 0.0430s
-- add_index("milestones", ["project_id"], {:name=>"index_milestones_on_project_id"})
-> 0.0623s
-- create_table("namespaces", {:force=>true})
-> 0.0286s
-- add_index("namespaces", ["name"], {:name=>"index_namespaces_on_name"})
-> 0.0370s
-- add_index("namespaces", ["owner_id"], {:name=>"index_namespaces_on_owner_id"})
-> 0.0515s
-- add_index("namespaces", ["path"], {:name=>"index_namespaces_on_path"})
-> 0.0625s
-- add_index("namespaces", ["type"], {:name=>"index_namespaces_on_type"})
-> 0.0827s
-- create_table("notes", {:force=>true})
-> 0.0331s
-- add_index("notes", ["commit_id"], {:name=>"index_notes_on_commit_id"})
-> 0.0583s
-- add_index("notes", ["created_at"], {:name=>"index_notes_on_created_at"})
-> 0.0551s
-- add_index("notes", ["noteable_type"], {:name=>"index_notes_on_noteable_type"})
-> 0.0448s
-- add_index("notes", ["project_id", "noteable_type"], {:name=>"index_notes_on_project_id_and_noteable_type"})
-> 0.0333s
-- add_index("notes", ["project_id"], {:name=>"index_notes_on_project_id"})
-> 0.0993s
-- create_table("projects", {:force=>true})
-> 0.0312s
-- add_index("projects", ["namespace_id"], {:name=>"index_projects_on_namespace_id"})
-> 0.0529s
-- add_index("projects", ["owner_id"], {:name=>"index_projects_on_owner_id"})
-> 0.0493s
-- create_table("protected_branches", {:force=>true})
-> 0.0310s
-- create_table("services", {:force=>true})
-> 0.0275s
-- add_index("services", ["project_id"], {:name=>"index_services_on_project_id"})
-> 0.0557s
-- create_table("snippets", {:force=>true})
-> 0.0326s
-- add_index("snippets", ["created_at"], {:name=>"index_snippets_on_created_at"})
-> 0.0364s
-- add_index("snippets", ["expires_at"], {:name=>"index_snippets_on_expires_at"})
-> 0.0476s
-- add_index("snippets", ["project_id"], {:name=>"index_snippets_on_project_id"})
-> 0.0432s
-- create_table("taggings", {:force=>true})
-> 0.0401s
-- add_index("taggings", ["tag_id"], {:name=>"index_taggings_on_tag_id"})
-> 0.0456s
-- add_index("taggings", ["taggable_id", "taggable_type", "context"], {:name=>"index_taggings_on_taggable_id_and_taggable_type_and_context"})
-> 0.0400s
-- create_table("tags", {:force=>true})
-> 0.0311s
-- create_table("users", {:force=>true})
-> 0.0276s
-- add_index("users", ["admin"], {:name=>"index_users_on_admin"})
-> 0.0500s
-- add_index("users", ["blocked"], {:name=>"index_users_on_blocked"})
-> 0.0559s
-- add_index("users", ["email"], {:name=>"index_users_on_email", :unique=>true})
-> 0.0506s
-- add_index("users", ["extern_uid", "provider"], {:name=>"index_users_on_extern_uid_and_provider", :unique=>true})
-> 0.0573s
-- add_index("users", ["name"], {:name=>"index_users_on_name"})
-> 0.0782s
-- add_index("users", ["reset_password_token"], {:name=>"index_users_on_reset_password_token", :unique=>true})
-> 0.0743s
-- add_index("users", ["username"], {:name=>"index_users_on_username"})
-> 0.1395s
-- create_table("users_projects", {:force=>true})
-> 0.0248s
-- add_index("users_projects", ["project_access"], {:name=>"index_users_projects_on_project_access"})
-> 0.0431s
-- add_index("users_projects", ["project_id"], {:name=>"index_users_projects_on_project_id"})
-> 0.0334s
-- add_index("users_projects", ["user_id"], {:name=>"index_users_projects_on_user_id"})
-> 0.0354s
-- create_table("web_hooks", {:force=>true})
-> 0.0295s
-- create_table("wikis", {:force=>true})
-> 0.0325s
-- add_index("wikis", ["project_id"], {:name=>"index_wikis_on_project_id"})
-> 0.0541s
-- add_index("wikis", ["slug"], {:name=>"index_wikis_on_slug"})
-> 0.0580s
-- initialize_schema_migrations_table()
-> 0.0904s
-- assume_migrated_upto_version(20121227190440, ["/opt/gitlab-4.0/db/migrate"])
-> 0.3891s
== Seed from /opt/gitlab-4.0/db/fixtures/production/001_admin.rb
Administrator account created:
login.........xxxxxxxxxx
password......xxxxxxxx
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
remote: Counting objects: 10, done.
remote: Compressing objects: 100% (8/ , done.
remote: Total 10 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (10/10), done.
[master d6ac126] GitLab
1 file changed, 9 insertions(+), 4 deletions(-)
Counting objects: 7, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 368 bytes, done.
Total 4 (delta 0), reused 0 (delta 0)
To git@localhost:gitolite-admin
9218422..d6ac126 master -> master
Done!
* Precompiling assests ...
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
|
Last edited by edouard.lopez on Sun Feb 17, 2013 8:27 pm; edited 1 time in total |
|
| Back to top |
|
 |
wildbug
n00b
Joined: 07 Oct 2007
Posts: 73
|
| Posted: Mon Feb 04, 2013 6:14 pm Post subject: |
|
|
I ran into this error, too, while trying out Gitlab. I'm not sure, but I think path the config script should be "chmodding" is the one to which you symlinked. My workaround was to simply create a ".gitolite" directory under repositories; this worked, and at the end of the installation, it was still empty.
After "fixing" the .gitolite issue, I got the same output as you posted above, complete with three "fatal: Not a git repo..." errors/warnings. I assumed it worked and the git warnings were not fatal.
The next error I got was this:
| Code: | # /etc/init.d/gitlab-4.0 start
* Starting GitLab 4.0 Unicorn servers ...
* /run/gitlab: creating directory
* /run/gitlab: correcting owner
Gemfile syntax error:
/opt/gitlab-4.0/Gemfile:14: syntax error, unexpected ':', expecting $end
gem "mysql2", group: :mysql |
Some googling led to a solution; that syntax is for Ruby 1.9, and Ruby 1.8 was the active interpreter on my system. Solution:
| Code: | # eselect ruby list
Available Ruby profiles:
[1] ruby18 (with Rubygems) *
[2] ruby19 (with Rubygems)
# eselect ruby set 2 |
Next, another error:
| Code: | # /etc/init.d/gitlab-4.0 restart
* Caching service dependencies ... [ ok ]
* Stopping GitLab 4.0 Resque worker ... [ ok ]
* Stopping GitLab 4.0 Unicorn servers ...
* start-stop-daemon: fopen `/run/gitlab/unicorn.pid': No such file or directory [ ok ]
* Starting GitLab 4.0 Unicorn servers ...
/opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/configurator.rb:74:in `read': No such file or directory - /opt/gitlab-4.0/config/unicorn.rb (Errno::ENOENT)
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/configurator.rb:74:in `reload'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/configurator.rb:67:in `initialize'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:107:in `new'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/lib/unicorn/http_server.rb:107:in `initialize'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/bin/unicorn_rails:209:in `new'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/gems/unicorn-4.4.0/bin/unicorn_rails:209:in `<top (required)>'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in `load'
from /opt/gitlab-4.0/vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in `<main>'
master failed to start, check stderr log for details
|
The solution to this one is to "cp /opt/gitlab-4.0/config/unicorn.rb{.example,}" and edit it to your settings. I had to change the 'app_dir' (to /opt/gitlab-4.0/) and 'listen' settings (to the port on which I want to access GitLab).
After that I was able to access the GitLabHQ application. The default user/pass are the ones you "xxx"ed out in the output above.
If you get the following error while (re)starting, you may need to kill unicorn manually:
| Code: | start-stop-daemon: fopen `/run/gitlab/unicorn.pid': No such file or directory
...
# kill $(cat /opt/gitlab-4.0/tmp/pids/unicorn.pid) |
|
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Sun Feb 17, 2013 3:09 pm Post subject: |
|
|
Hi,
I’m author of this ebuild. I’ve just fixed the issue with repos_path (see cvut/gentoo-overlay#1) – .gitolite directory is under Gitolite’s home (/var/lib/gitolite by default), not repository path (/var/lib/gitolite/repositories).
These git errors (lines fatal: Not a git repository (or any of the parent directories): .git) are actually „ok“, it’s bug in bundler (see carlhuda/bundler#1787) that expects git repository in GitLab’s home. If it annoys you, simply create empty git repository (git init) under /opt/gitlab-4.0 or clone upstrem’s repository. I’ve add info message to the end of config phase. |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Sun Feb 17, 2013 4:21 pm Post subject: |
|
|
| hi i wrote the wiki.gentoo.org git page (and sudo, and rails + passenger, and others) and will next weekend adapt it for gitlab, no overlay or ebuilds required. my friend set up an ubuntu server (that acted rather corrupted) with gitlab working, so were gonna migrate it over to gentoo. just give it a little time and you'll have redundant solutions to your problem. |
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Sun Feb 17, 2013 4:25 pm Post subject: |
|
|
| 666threesixes666 wrote: | | no overlay or ebuilds required… you'll have redundant solutions to your problem. |
Heh, sure, it’s better to follow looong manual full of commands to run instead of run single ebuild that do it all…  |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Sun Feb 17, 2013 5:10 pm Post subject: |
|
|
| yes working software is better than broken ebuilds. last i checked passenger ebuild failed and long string of commands worked. gitolites ebuild messes with the git user and places your repositories in a strange location that is not compatible with git's official documentation. |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Sun Feb 17, 2013 8:26 pm Post subject: |
|
|
I was going to drop a note about your github update, but you already did.
Thanks |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Sun Feb 17, 2013 8:49 pm Post subject: |
|
|
I'm still having issue with the install step :
| Code: | | sudo emerge --config "=www-apps/gitlabhq-4.0.0-r2" |
First I got an error about the default revision :
| Quote: | Configuring pkg...
* Checking configuration files
* Copying git hook to /var/lib/gitolite/.gitolite/hooks/
* Initializing database ...
gitlab already exists
fatal: bad default revision 'HEAD'
-- create_table("events", {:force=>true})
-> 0.0769s
-- add_index("events", ["action"], {:name=>"index_events_on_action"})
-> 0.0584s
-- add_index("events", ["author_id"], {:name=>"index_events_on_author_id"})
-> 0.0533s
-- add_index("events", ["created_at"], {:name=>"index_events_on_created_at"})
-> 0.0633s
-- add_index("events", ["project_id"], {:name=>"index_events_on_project_id"})
-> 0.0853s
-- add_index("events", ["target_id"], {:name=>"index_events_on_target_id"})
-> 0.0666s
-- add_index("events", ["target_type"], {:name=>"index_events_on_target_type"})
-> 0.0660s
-- create_table("issues", {:force=>true})
-> 0.0481s
-- add_index("issues", ["assignee_id"], {:name=>"index_issues_on_assignee_id"})
-> 0.0368s
-- add_index("issues", ["author_id"], {:name=>"index_issues_on_author_id"})
-> 0.0477s
-- add_index("issues", ["closed"], {:name=>"index_issues_on_closed"})
-> 0.0533s
-- add_index("issues", ["created_at"], {:name=>"index_issues_on_created_at"})
-> 0.0884s
-- add_index("issues", ["milestone_id"], {:name=>"index_issues_on_milestone_id"})
-> 0.0532s
-- add_index("issues", ["project_id"], {:name=>"index_issues_on_project_id"})
-> 0.1052s
-- add_index("issues", ["title"], {:name=>"index_issues_on_title"})
-> 0.0666s
-- create_table("keys", {:force=>true})
-> 0.0194s
-- add_index("keys", ["identifier"], {:name=>"index_keys_on_identifier"})
-> 0.0496s
-- add_index("keys", ["project_id"], {:name=>"index_keys_on_project_id"})
-> 0.0663s
-- add_index("keys", ["user_id"], {:name=>"index_keys_on_user_id"})
-> 0.0344s
-- create_table("merge_requests", {:force=>true})
-> 0.0489s
-- add_index("merge_requests", ["assignee_id"], {:name=>"index_merge_requests_on_assignee_id"})
-> 0.0565s
-- add_index("merge_requests", ["author_id"], {:name=>"index_merge_requests_on_author_id"})
-> 0.0543s
-- add_index("merge_requests", ["closed"], {:name=>"index_merge_requests_on_closed"})
-> 0.0502s
-- add_index("merge_requests", ["created_at"], {:name=>"index_merge_requests_on_created_at"})
-> 0.0734s
-- add_index("merge_requests", ["milestone_id"], {:name=>"index_merge_requests_on_milestone_id"})
-> 0.0683s
-- add_index("merge_requests", ["project_id"], {:name=>"index_merge_requests_on_project_id"})
-> 0.0701s
-- add_index("merge_requests", ["source_branch"], {:name=>"index_merge_requests_on_source_branch"})
-> 0.0618s
-- add_index("merge_requests", ["target_branch"], {:name=>"index_merge_requests_on_target_branch"})
-> 0.0912s
-- add_index("merge_requests", ["title"], {:name=>"index_merge_requests_on_title"})
-> 0.1006s
-- create_table("milestones", {:force=>true})
-> 0.0573s
-- add_index("milestones", ["due_date"], {:name=>"index_milestones_on_due_date"})
-> 0.0465s
-- add_index("milestones", ["project_id"], {:name=>"index_milestones_on_project_id"})
-> 0.0406s
-- create_table("namespaces", {:force=>true})
-> 0.0627s
-- add_index("namespaces", ["name"], {:name=>"index_namespaces_on_name"})
-> 0.0510s
-- add_index("namespaces", ["owner_id"], {:name=>"index_namespaces_on_owner_id"})
-> 0.0590s
-- add_index("namespaces", ["path"], {:name=>"index_namespaces_on_path"})
-> 0.0650s
-- add_index("namespaces", ["type"], {:name=>"index_namespaces_on_type"})
-> 0.0677s
-- create_table("notes", {:force=>true})
-> 0.0297s
-- add_index("notes", ["commit_id"], {:name=>"index_notes_on_commit_id"})
-> 0.0538s
-- add_index("notes", ["created_at"], {:name=>"index_notes_on_created_at"})
-> 0.0748s
-- add_index("notes", ["noteable_type"], {:name=>"index_notes_on_noteable_type"})
-> 0.0740s
-- add_index("notes", ["project_id", "noteable_type"], {:name=>"index_notes_on_project_id_and_noteable_type"})
-> 0.0592s
-- add_index("notes", ["project_id"], {:name=>"index_notes_on_project_id"})
-> 0.0608s
-- create_table("projects", {:force=>true})
-> 0.0634s
-- add_index("projects", ["namespace_id"], {:name=>"index_projects_on_namespace_id"})
-> 0.0365s
-- add_index("projects", ["owner_id"], {:name=>"index_projects_on_owner_id"})
-> 0.0561s
-- create_table("protected_branches", {:force=>true})
-> 0.0407s
-- create_table("services", {:force=>true})
-> 0.0416s
-- add_index("services", ["project_id"], {:name=>"index_services_on_project_id"})
-> 0.0365s
-- create_table("snippets", {:force=>true})
-> 0.0635s
-- add_index("snippets", ["created_at"], {:name=>"index_snippets_on_created_at"})
-> 0.0592s
-- add_index("snippets", ["expires_at"], {:name=>"index_snippets_on_expires_at"})
-> 0.0600s
-- add_index("snippets", ["project_id"], {:name=>"index_snippets_on_project_id"})
-> 0.0653s
-- create_table("taggings", {:force=>true})
-> 0.0406s
-- add_index("taggings", ["tag_id"], {:name=>"index_taggings_on_tag_id"})
-> 0.0289s
-- add_index("taggings", ["taggable_id", "taggable_type", "context"], {:name=>"index_taggings_on_taggable_id_and_taggable_type_and_context"})
-> 0.0586s
-- create_table("tags", {:force=>true})
-> 0.0369s
-- create_table("users", {:force=>true})
-> 0.0513s
-- add_index("users", ["admin"], {:name=>"index_users_on_admin"})
-> 0.0497s
-- add_index("users", ["blocked"], {:name=>"index_users_on_blocked"})
-> 0.0500s
-- add_index("users", ["email"], {:name=>"index_users_on_email", :unique=>true})
-> 0.0770s
-- add_index("users", ["extern_uid", "provider"], {:name=>"index_users_on_extern_uid_and_provider", :unique=>true})
-> 0.0601s
-- add_index("users", ["name"], {:name=>"index_users_on_name"})
-> 0.0949s
-- add_index("users", ["reset_password_token"], {:name=>"index_users_on_reset_password_token", :unique=>true})
-> 0.0790s
-- add_index("users", ["username"], {:name=>"index_users_on_username"})
-> 0.0759s
-- create_table("users_projects", {:force=>true})
-> 0.0465s
-- add_index("users_projects", ["project_access"], {:name=>"index_users_projects_on_project_access"})
-> 0.0449s
-- add_index("users_projects", ["project_id"], {:name=>"index_users_projects_on_project_id"})
-> 0.0509s
-- add_index("users_projects", ["user_id"], {:name=>"index_users_projects_on_user_id"})
-> 0.0632s
-- create_table("web_hooks", {:force=>true})
-> 0.0306s
-- create_table("wikis", {:force=>true})
-> 0.0251s
-- add_index("wikis", ["project_id"], {:name=>"index_wikis_on_project_id"})
-> 0.0366s
-- add_index("wikis", ["slug"], {:name=>"index_wikis_on_slug"})
-> 0.0414s
-- initialize_schema_migrations_table()
-> 0.0002s
-- assume_migrated_upto_version(20121227190440, ["/opt/gitlab-4.0/db/migrate"])
-> 0.0008s
== Seed from /opt/gitlab-4.0/db/fixtures/production/001_admin.rb |
But it continue and then I get a problem on the password.
- what is this login and password about ? Where would I need it ?
- Second there is a prompt for a password. What is it ? a confirmation ?
- Whatever I do (put my user password, the db password or nothing), it ultimately finish to spit some more errors
Below is the output when I tried to use my user (whoami) password. Hence the 'permission denied' at the end.
| Quote: | Administrator account created:
login.........admin@local.host
password......xxxxxx
Password:
Password: rake aborted!
gitolite timeout
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:77:in `rescue in apply'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:24:in `apply'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:185:in `admin_all_repo!'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite.rb:45:in `enable_automerge'
/opt/gitlab-4.0/lib/tasks/gitlab/enable_automerge.rake:4:in `block (2 levels) in <top (required)>'
Tasks: TOP => gitlab:app:setup => gitlab:enable_automerge
(See full trace by running task with --trace)
* ERROR: www-apps/gitlabhq-4.0.0-r2 failed (config phase):
* failed to run rake gitlab:app:setup
*
* Call stack:
* ebuild.sh, line 93: Called pkg_config
* environment, line 4737: Called die
* The specific snippet of code:
* ${BUNDLE} exec rake gitlab:app:setup RAILS_ENV=${RAILS_ENV}" || die "failed to run rake gitlab:app:setup";
*
* If you need support, post the output of `emerge --info '=www-apps/gitlabhq-4.0.0-r2'`,
* the complete build log and the output of `emerge -pqv '=www-apps/gitlabhq-4.0.0-r2'`.
* This ebuild is from an overlay named 'cvut': '/var/db/pkg/'
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
* The complete build log is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2/temp/environment'.
* Working directory: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2'
* S: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r2/work/gitlabhq-4.0.0'
Password:
Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists. |
When I try to reach my gitlab install I got Passenger error
| Quote: | Passenger encountered the following error:
The application spawner server exited unexpectedly: Unexpected end-of-file detected.
Exception class:
PhusionPassenger::Rack::ApplicationSpawner::Error
Backtrace:
# File Line Location
0 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/rack/application_spawner.rb 135 in `rescue in start'
1 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/rack/application_spawner.rb 130 in `start'
2 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 253 in `block (2 levels) in spawn_rack_application'
3 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server_collection.rb 132 in `lookup_or_add'
4 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 246 in `block in spawn_rack_application'
5 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server_collection.rb 82 in `block in synchronize'
6 prelude> 10:in `synchronize'
7 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server_collection.rb 79 in `synchronize'
8 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 244 in `spawn_rack_application'
9 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 137 in `spawn_application'
10 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 275 in `handle_spawn_application'
11 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server.rb 357 in `server_main_loop'
12 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server.rb 206 in `start_synchronously'
13 /usr/libexec/passenger/bin/passenger-spawn-server 99 in `' |
|
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Tue Feb 19, 2013 6:11 pm Post subject: |
|
|
| edouard.lopez wrote: | I'm still having issue with the install step :
| Code: | | sudo emerge --config "=www-apps/gitlabhq-4.0.0-r2" |
|
You’re still using the old ebuild, new one is revision 3, i.e. www-apps/gitlabhq-4.0.0-r3 (see Gentoo Handbook for more info about ebuild names, versioning etc.) Did you updated Overlay (layman -s cvut) and reinstalled the package?
| edouard.lopez wrote: |
First I got an error about the default revision :
| Code: | | fatal: bad default revision 'HEAD' |
|
This is most likely another false error caused by Bundler (still the same carlhuda/bundler#1787), just ignore it. If it will not be fixed soon, I’m gonna add workaround to the ebuild that will simple initialize empty git repository in GitLab’s home directory or copy actual GitLab’s repository there.
| edouard.lopez wrote: |
what is this login and password about ? Where would I need it ?
|
Do you mean user admin@local.host with default password 5iveL!fe? This is GitLab’s default admin account, you need it to log-in into GitLab for the first time…
| edouard.lopez wrote: |
When I try to reach my gitlab install I got Passenger error
| Code: |
Passenger encountered the following error:
The application spawner server exited unexpectedly: Unexpected end-of-file detected.
Exception class:
PhusionPassenger::Rack::ApplicationSpawner::Error
|
|
Uh, this error can mean many things. Try to install GitLab with fixed ebuild, then we’ll see. |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Wed Feb 20, 2013 2:09 am Post subject: |
|
|
| after trashing my friends VM i built up for em, i can understand why its not supported. emerge doesnt like python 2.7, and gitlab doesnt like python 3.2. i think its possible to get everything running together in harmony, so long as you merge everything before starting on getting gitlab up. i got up to the point of databases from https://github.com/gitlabhq/gitlabhq/blob/stable/doc/install/installation.md this guide.... i know gems can run independent of portage to install goodies. im going to the restore point then going to merge everything before trying to finish off gitlab again.... |
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Wed Feb 20, 2013 2:18 am Post subject: |
|
|
| 666threesixes666 wrote: | | emerge doesnt like python 2.7, and gitlab doesnt like python 3.2. |
I have 3.2 as default Python on my system (2.7 installed too) and don’t have any problems with GitLab (when installing from my ebuild with some patches for Gentoo, but not Python related).
To edouard.lopez:
I just realized, there’s one common issue with Gentoo and Ruby - RUBY_OPT environment variable (see /etc/env.d/10rubygems) that is set to -rauto_gem. I don’t know why is there by default, but it breaks many Ruby applications. Make sure that you have this variable empty. |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Wed Feb 20, 2013 8:32 am Post subject: |
|
|
So I edited /etc/env.d/10rubygems to empty string and then run :
| Code: | | sudo emerge -va gitlabhq; sudo emerge --config "=www-apps/gitlabhq-4.0.0-r3" |
Ignoring the message you said were irrelevant, I still got the the following output that won't give back the prompt :
| Quote: | Administrator account created:
login.........admin@local.host
password......5iveL!fe
Password: rake aborted!
gitolite timeout
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:77:in `rescue in apply'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:24:in `apply'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:185:in `admin_all_repo!'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite.rb:45:in `enable_automerge'
/opt/gitlab-4.0/lib/tasks/gitlab/enable_automerge.rake:4:in `block (2 levels) in <top (required)>'
Tasks: TOP => gitlab:app:setup => gitlab:enable_automerge
(See full trace by running task with --trace)
* ERROR: www-apps/gitlabhq-4.0.0-r3 failed (config phase):
* failed to run rake gitlab:app:setup
*
* Call stack:
* ebuild.sh, line 93: Called pkg_config
* environment, line 4737: Called die
* The specific snippet of code:
* ${BUNDLE} exec rake gitlab:app:setup RAILS_ENV=${RAILS_ENV}" || die "failed to run rake gitlab:app:setup";
*
* If you need support, post the output of `emerge --info '=www-apps/gitlabhq-4.0.0-r3'`,
* the complete build log and the output of `emerge -pqv '=www-apps/gitlabhq-4.0.0-r3'`.
* This ebuild is from an overlay named 'cvut': '/var/db/pkg/'
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
* The complete build log is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/temp/environment'.
* Working directory: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3'
* S: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work/gitlabhq-4.0.0' |
|
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Wed Feb 20, 2013 1:52 pm Post subject: |
|
|
To edouard.lopez:
There’s some problem with your Gitolite. Check Gitolite’s log in /var/log/gitolite/ (or /var/lib/gitolite/.gitolite/logs/) and GitLab’s logs in /var/log/gitlab-4.0/.
However, it’s weird. I’ve installed it just few days ago without any problem. GitLab ebuild is checking if there’s git user with correct home directory according to yours GitLab settings etc. so it should be ok. Wait a moment… try to unmerge gitlab and gitolite, delete whole /var/lib/gitolite and then emerge it again. Ebuild is not re-initializing Gitolite when it’s already initialized (to not accidentally delete all your precious repositories) so if you did something wrong previously, there may be the problem. Also make sure that you’re installing dev-vcs/gitolite with USE gitlab from CVUT Overlay – GitLab has few modifications in default configuration. |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Wed Feb 20, 2013 11:24 pm Post subject: |
|
|
So I unmerge `gitlabhq` and `gitolite`
| Code: | | emerge --unmerge www-apps/gitlabhq dev-vcs/gitolite |
Remove the gitolite directory
| Code: | | rm /var/lib/gitolite/ -rf |
And reinstall `gitlabhq`
| Code: | | emerge -va gitlabhq |
And here is what is going to be install (package from the CVUT )
| Quote: | Calculating dependencies... done!
[ebuild N ~] dev-vcs/gitolite-3.2::cvut USE="gitlab -tools -vim-syntax" 0 kB
[ebuild N ~] www-apps/gitlabhq-4.0.0-r3:4.0::cvut USE="mysql perf-patch unicorn -analytics -memcached -postgres -public-projects" RUBY_TARGETS="ruby19" 0 kB |
Starting the install, I got the following :
| Quote: | >>> Emerging (1 of 2) dev-vcs/gitolite-3.2 from cvut
* gitolite-3.2.tar.gz SHA256 SHA512 WHIRLPOOL size ... [ ok ]
>>> Unpacking source...
>>> Unpacking gitolite-3.2.tar.gz to /var/tmp/portage/dev-vcs/gitolite-3.2/work
>>> Source unpacked in /var/tmp/portage/dev-vcs/gitolite-3.2/work
>>> Preparing source in /var/tmp/portage/dev-vcs/gitolite-3.2/work/gitolite-3.2 ...
* Applying gitolite-3.2-gitlab.patch ... [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-vcs/gitolite-3.2/work/gitolite-3.2 ...
* No Make or Build file detected...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-vcs/gitolite-3.2/work/gitolite-3.2 ...
>>> Source compiled.
>>> Test phase [not enabled]: dev-vcs/gitolite-3.2
>>> Install gitolite-3.2 into /var/tmp/portage/dev-vcs/gitolite-3.2/image/ category dev-vcs
>>> Completed installing gitolite-3.2 into /var/tmp/portage/dev-vcs/gitolite-3.2/image/
ecompressdir: bzip2 -9 /usr/share/doc
>>> Installing (1 of 2) dev-vcs/gitolite-3.2
* checking 73 files for package collisions
>>> Merging dev-vcs/gitolite-3.2 to /
--- /var/
--- /var/lib/
>>> /var/lib/gitolite/
>>> /var/lib/gitolite/.keep_dev-vcs_gitolite-0
--- /var/log/
--- /var/log/gitolite/
>>> /var/log/gitolite/.keep_dev-vcs_gitolite-0
--- /usr/
--- /usr/bin/
--- /usr/lib64/
--- /usr/lib64/perl5/
--- /usr/lib64/perl5/vendor_perl/
--- /usr/lib64/perl5/vendor_perl/5.12.4/
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Conf/
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Conf/Explode.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Conf/Store.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Conf/Sugar.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Conf/Load.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Hooks/
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Hooks/PostUpdate.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Hooks/Update.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Rc.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Conf.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Setup.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Easy.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/RefexExpr.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/Writable.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/Alias.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/Mirroring.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/CpuTime.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/Shell.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Triggers/RepoUmask.pm
>>> /usr/lib64/perl5/vendor_perl/5.12.4/Gitolite/Common.pm
--- /usr/share/
--- /usr/share/doc/
>>> /usr/share/doc/gitolite-3.2/
>>> /usr/share/doc/gitolite-3.2/README.txt.bz2
>>> /usr/share/doc/gitolite-3.2/CHANGELOG.bz2
--- /usr/libexec/
>>> /usr/libexec/gitolite/
>>> /usr/libexec/gitolite/VREF/
>>> /usr/libexec/gitolite/VREF/lock
>>> /usr/libexec/gitolite/VREF/COUNT
>>> /usr/libexec/gitolite/VREF/MAX_NEWBIN_SIZE
>>> /usr/libexec/gitolite/VREF/VOTES
>>> /usr/libexec/gitolite/VREF/MERGE-CHECK
>>> /usr/libexec/gitolite/VREF/refex-expr
>>> /usr/libexec/gitolite/VREF/EMAIL-CHECK
>>> /usr/libexec/gitolite/VREF/FILETYPE
>>> /usr/libexec/gitolite/VREF/partial-copy
>>> /usr/libexec/gitolite/gitolite-shell
>>> /usr/libexec/gitolite/gitolite
>>> /usr/libexec/gitolite/triggers/
>>> /usr/libexec/gitolite/triggers/bg
>>> /usr/libexec/gitolite/triggers/upstream
>>> /usr/libexec/gitolite/triggers/renice
>>> /usr/libexec/gitolite/triggers/post-compile/
>>> /usr/libexec/gitolite/triggers/post-compile/update-git-daemon-access-list
>>> /usr/libexec/gitolite/triggers/post-compile/update-description-file
>>> /usr/libexec/gitolite/triggers/post-compile/ssh-authkeys-shell-users
>>> /usr/libexec/gitolite/triggers/post-compile/ssh-authkeys
>>> /usr/libexec/gitolite/triggers/post-compile/update-gitweb-access-list
>>> /usr/libexec/gitolite/triggers/post-compile/update-git-configs
>>> /usr/libexec/gitolite/triggers/post-compile/ssh-authkeys-split
>>> /usr/libexec/gitolite/triggers/partial-copy
>>> /usr/libexec/gitolite/commands/
>>> /usr/libexec/gitolite/commands/D
>>> /usr/libexec/gitolite/commands/desc
>>> /usr/libexec/gitolite/commands/fork
>>> /usr/libexec/gitolite/commands/help
>>> /usr/libexec/gitolite/commands/info
>>> /usr/libexec/gitolite/commands/lock
>>> /usr/libexec/gitolite/commands/push
>>> /usr/libexec/gitolite/commands/sskm
>>> /usr/libexec/gitolite/commands/sudo
>>> /usr/libexec/gitolite/commands/creator
>>> /usr/libexec/gitolite/commands/perms
>>> /usr/libexec/gitolite/commands/rsync
>>> /usr/libexec/gitolite/commands/svnserve
>>> /usr/libexec/gitolite/commands/htpasswd
>>> /usr/libexec/gitolite/commands/git-config
>>> /usr/libexec/gitolite/commands/symbolic-ref
>>> /usr/libexec/gitolite/commands/access
>>> /usr/libexec/gitolite/commands/list-dangling-repos
>>> /usr/libexec/gitolite/commands/mirror
>>> /usr/libexec/gitolite/commands/sshkeys-lint
>>> /usr/libexec/gitolite/commands/who-pushed
>>> /usr/libexec/gitolite/commands/writable
>>> /usr/libexec/gitolite/commands/print-default-rc
>>> /usr/libexec/gitolite/VERSION
>>> /usr/libexec/gitolite/syntactic-sugar/
>>> /usr/libexec/gitolite/syntactic-sugar/continuation-lines
>>> /usr/libexec/gitolite/syntactic-sugar/keysubdirs-as-groups
>>> /usr/bin/gitolite-shell -> /usr/libexec/gitolite/gitolite-shell
>>> /usr/bin/gitolite -> /usr/libexec/gitolite/gitolite
*
* Please make sure that your 'git' user has the correct homedir (/var/lib/gitolite).
* Especially if you're migrating from gitosis.
*
* Change your user ID to 'git' and run 'gitolite setup -h' to show how
* to setup Gitolite.
>>> dev-vcs/gitolite-3.2 merged.
>>> Emerging (2 of 2) www-apps/gitlabhq-4.0.0-r3 from cvut
>>> Unpacking source...
* Running unpack phase for all ...
remote: Counting objects: 136, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 85 (delta 65), reused 56 (delta 36)
Unpacking objects: 100% (85/85), done.
From https://github.com/gitlabhq/gitlabhq
08f665c..ba1a453 master -> master
GIT update -->
repository: https://github.com/gitlabhq/gitlabhq.git
updating from commit: 08f665cf2876c70a2a987a498b01d00de7478e4a
to commit: ba1a453ef3dddf50a2c118f4490267b19a0b2cc8
app/models/project.rb | 2 +-
app/views/commits/_commit.html.haml | 2 +-
db/fixtures/development/09_issues.rb | 2 +-
db/fixtures/development/10_merge_requests.rb | 2 +-
doc/api/projects.md | 2 +-
doc/install/installation.md | 2 +-
lib/api/projects.rb | 5 +--
spec/requests/api/projects_spec.rb | 70 ++++++++++++++++++++++++++++++---------
8 files changed, 64 insertions(+), 23 deletions(-)
commit: 708a0d421e42522c6f10ff272d40db36b2205d96
branch: master
storage directory: "/usr/portage/distfiles/egit-src/gitlabhq.git"
checkout type: bare repository
Cloning into '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work/all/gitlabhq-4.0.0'...
done.
Switched to a new branch 'tree-708a0d421e42522c6f10ff272d40db36b2205d96'
>>> Unpacked to /var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work/all/gitlabhq-4.0.0
>>> Source unpacked in /var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work
>>> Preparing source in /var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work ...
* Running prepare phase for all ...
* Applying gitlabhq-4.0.0-r1-fix-gemfile.patch ... [ ok ]
* Applying gitlabhq-4.0.0-fix-checks-gentoo.patch ... [ ok ]
* Applying gitlabhq-4.0.0-fix-passenger.patch ... [ ok ]
* Applying gitlabhq-4.0.0-performance.patch ... [ ok ]
* Running source copy phase for ruby19 ...
* Running prepare phase for ruby19 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work ...
>>> Source compiled.
>>> Test phase [not enabled]: www-apps/gitlabhq-4.0.0-r3
>>> Install gitlabhq-4.0.0-r3 into /var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/image/ category www-apps
* Running install phase for ruby19 ...
* Running bundle install --deployment --without development test thin memcached postgres ...
Fetching gem metadata from http://rubygems.org/........
Fetching gem metadata from http://rubygems.org/..
Fetching https://github.com/ISSIntel/charlock_holmes.git
remote: Counting objects: 637, done.
remote: Compressing objects: 100% (249/249), done.
....
|
Then it fecth and install tenth of gems and It finishes on the message related to each package.
However, something hit me that time :
| Quote: | * Change your user ID to 'git' and run 'gitolite setup -h' to show how
* to setup Gitolite. |
So, do I need to do anything about gitolite ? I was expecting the ebuild to do all the setup.
Just to be sure I checked users path in /etc/passwd :
| Quote: | git:x:104:121:added by portage for gitolite:/var/lib/gitolite:/bin/sh
redis:x:75:75:added by portage for redis:/var/lib/redis:/sbin/nologin
gitlab:x:105:120:added by portage for gitlabhq:/home/gitlab:/bin/bash
gitdaemon:x:1006:121::/dev/null:/sbin/nologin
|
Then I run the configuration for `gitlabhq`
| Code: | | emerge --config "=www-apps/gitlabhq-4.0.0-r3" |
And get the same issue : - prompt is asking for a password (but who/for what ?) ;
- rake abort ;
- gitolite timeout.
| Quote: | Administrator account created:
login.........admin@local.host
password......5iveL!fe
Password: rake aborted!
gitolite timeout
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:77:in `rescue in apply'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:24:in `apply'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite_config.rb:185:in `admin_all_repo!'
/opt/gitlab-4.0/lib/gitlab/backend/gitolite.rb:45:in `enable_automerge'
/opt/gitlab-4.0/lib/tasks/gitlab/enable_automerge.rake:4:in `block (2 levels) in <top (required)>'
Tasks: TOP => gitlab:app:setup => gitlab:enable_automerge
(See full trace by running task with --trace)
* ERROR: www-apps/gitlabhq-4.0.0-r3 failed (config phase):
* failed to run rake gitlab:app:setup
*
* Call stack:
* ebuild.sh, line 93: Called pkg_config
* environment, line 4737: Called die
* The specific snippet of code:
* ${BUNDLE} exec rake gitlab:app:setup RAILS_ENV=${RAILS_ENV}" || die "failed to run rake gitlab:app:setup";
*
* If you need support, post the output of `emerge --info '=www-apps/gitlabhq-4.0.0-r3'`,
* the complete build log and the output of `emerge -pqv '=www-apps/gitlabhq-4.0.0-r3'`.
* This ebuild is from an overlay named 'cvut': '/var/db/pkg/'
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
* The complete build log is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/temp/environment'.
* Working directory: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3'
* S: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work/gitlabhq-4.0.0'
Password:
Password:
Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists. |
|
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Thu Feb 21, 2013 2:35 am Post subject: |
|
|
| edouard.lopez wrote: | So I unmerge `gitlabhq` and `gitolite`
However, something hit me that time :
| Quote: | * Change your user ID to 'git' and run 'gitolite setup -h' to show how
* to setup Gitolite. |
So, do I need to do anything about gitolite ? I was expecting the ebuild to do all the setup.
|
This is postinstall message of gitolite ebuild (it can be used even without GitLab). While you’re using Gitolite only with GitLab, you don’t have to care about it, gitlab ebuild initializes gitolite for you.
| Quote: | git:x:104:121:added by portage for gitolite:/var/lib/gitolite:/bin/sh
redis:x:75:75:added by portage for redis:/var/lib/redis:/sbin/nologin
gitlab:x:105:120:added by portage for gitlabhq:/home/gitlab:/bin/bash
gitdaemon:x:1006:121::/dev/null:/sbin/nologin
|
There’s the problem! The ebuild installs GitLab to /opt/gitlab-4.0 and it should be gitlab’s user home directory as well (ebuild take care of it of course, but not when gitolite user already exists). Sure, that you can change this as you want, but did you actually? If not, change this to /opt/gitlab-4.0, move .ssh and .gitconfig to /opt/gitlab-4.0, erase /var/lib/gitolite and then run emerge --config once again. I’m almost sure that it will work now.  (I should add check for gitlab home directory to ebuild.)
| edouard.lopez wrote: |
And get the same issue : [list][*]prompt is asking for a password (but who/for what ?) ;
|
In this phase, GitLab is trying to pull from Gitolite (repo gitolite-admin.git) and should be authenticated with its SSH key. However, as you see, this fails so Gitolite (more precisely, SSHd daemon) asks for password instead.
In pkg_postinst phase, ebuild generates SSH key for gitlab user and stores it in DEST_DIR, i.e. /opt/gitlab-4.0/. The key is then used in Gitolite as the admin key (during gitolite initialization in pkg_config phase). The problem is that SSH client is looking into ~/.ssh for the key be default, but you’re gitlab’s home directory is /home/gitlab, not /opt/gitlab-4.0 where is the key! |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Thu Feb 21, 2013 8:33 am Post subject: |
|
|
I changed the gitlab home to `/home/gitlab/`, so I correct it :
| Code: | | usermod --home /opt/gitlab-4.0 gitlab |
Then copy and delete /home/gitlab/.ssh to /opt/gitlab-4.0
| Code: | cp -R /home/gitlab/.ssh /opt/gitlab-4.0
rm /home/gitlab/ -rf
|
Remove the gitolite directory
| Code: | | rm /var/lib/gitolite -rf |
And run the config again
| Code: | emerge --config "=www-apps/gitlabhq-4.0.0-r3"
|
I got the following statement (I put everything so it can help you prevent error):
| Quote: | Configuring pkg...
* Checking configuration files
* Gitolite's repos_path from gitlab.yml is not in the HOME of
* git user in passwd
* ERROR: www-apps/gitlabhq-4.0.0-r3 failed (config phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 93: Called pkg_config
* environment, line 4713: Called die
* The specific snippet of code:
* die;
*
* If you need support, post the output of `emerge --info '=www-apps/gitlabhq-4.0.0-r3'`,
* the complete build log and the output of `emerge -pqv '=www-apps/gitlabhq-4.0.0-r3'`.
* This ebuild is from an overlay named 'cvut': '/var/db/pkg/'
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
* The complete build log is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/temp/environment'.
* Working directory: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3'
* S: '/var/tmp/portage/www-apps/gitlabhq-4.0.0-r3/work/gitlabhq-4.0.0'
|
Here is the section about my gitolite in gitlab.yml :
| Code: | | vim /etc/gitlab-4.0/gitlab.yml |
| Quote: | gitolite:
admin_uri: git@localhost:gitolite-admin
repos_path: /var/lib/gitolite/repositories/
hooks_path: /var/lib/gitolite/.gitolite/hooks/
admin_key: gitlab
upload_pack: true
receive_pack: true
ssh_user: git
ssh_host: localhost
|
So I will try from the begining (--unmerge, then emerge back).
After the installing and before running the `emerge --config`, the repos_path: /var/lib/gitolite/repositories/ doesn't exists.
Ok, seems better :
| Quote: | Administrator account created:
login.........admin@local.host
password......5iveL!fe
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
remote: Counting objects: 6, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 6 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (6/6), done.
[master 591c31f] GitLab
1 file changed, 9 insertions(+), 4 deletions(-)
Counting objects: 7, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 367 bytes, done.
Total 4 (delta 0), reused 0 (delta 0)
To git@localhost:gitolite-admin
aa016ae..591c31f master -> master
Done!
* Precompiling assests ...
fatal: bad default revision 'HEAD'
|
Take some times, before displaying
| Quote: | | * GitLab is prepared, now you should configure your web server |
This part seems good, execpt it won't give back the prompt. Should I interrupt ? |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Thu Feb 21, 2013 9:52 am Post subject: |
|
|
Here is the output of my site when I try to reach gitlab (notice the footer).
[IMG]http://i.imgur.com/2mXB8ES.png[/IMG]
| Quote: | Passenger encountered the following error:
The application spawner server exited unexpectedly: Unexpected end-of-file detected.
Exception class:
PhusionPassenger::Rack::ApplicationSpawner::Error
Backtrace:
# File Line Location
0 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/rack/application_spawner.rb 135 in `rescue in start'
1 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/rack/application_spawner.rb 130 in `start'
2 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 253 in `block (2 levels) in spawn_rack_application'
3 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server_collection.rb 132 in `lookup_or_add'
4 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 246 in `block in spawn_rack_application'
5 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server_collection.rb 82 in `block in synchronize'
6 prelude> 10:in `synchronize'
7 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server_collection.rb 79 in `synchronize'
8 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 244 in `spawn_rack_application'
9 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 137 in `spawn_application'
10 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/spawn_manager.rb 275 in `handle_spawn_application'
11 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server.rb 357 in `server_main_loop'
12 /usr/lib64/ruby/site_ruby/1.9.1/phusion_passenger/abstract_server.rb 206 in `start_synchronously'
13 /usr/libexec/passenger/bin/passenger-spawn-server 99 in `'
Powered by Phusion Passenger, mod_rails / mod_rack for Apache.
|
I thought passenger was a Nginx module, so why does it talk about Apache then ?
| Quote: | | Powered by Phusion Passenger, mod_rails / mod_rack for Apache. |
|
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Thu Feb 21, 2013 3:38 pm Post subject: |
|
|
| edouard.lopez wrote: |
I thought passenger was a Nginx module, so why does it talk about Apache then ?
| Quote: | | Powered by Phusion Passenger, mod_rails / mod_rack for Apache. |
|
Passenger is for nginx and Apache2 as well. How did you install Passenger? Did you used my nginx ebuild with added Passenger module?
It should work with Passenger’s installer script as well, but I’ve never installed it this way and don’t recommend it (we’re using package managers for reason). I’m using nginx with Passenger on many servers so it really should work for you as well (I hope so). If not, I’m gonna ask you for access to your server, ’cause it’s nearly impossible how many problems you’ve hit. XD |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Fri Feb 22, 2013 10:21 pm Post subject: |
|
|
https://wiki.gentoo.org/wiki/Gitlab
i started it, and it looks like someone else finished it.... ill be testing this all the way later on tonight..... before i ran into problems on the ruby gem package section... (around 6.7 on the official page) |
|
| Back to top |
|
|
edouard.lopez
n00b
Joined: 26 Jan 2013
Posts: 8
Location: France
|
| Posted: Mon Feb 25, 2013 10:53 am Post subject: |
|
|
@jirutka is it possible to use your ebuild without Passenger ?
I'm trying to use the native vhost config with the ebuild by jirutka:
| Code: | server {
listen 0.0.0.0:81; # default_server; # e.g., listen 192.168.1.1:80;
server_name git.my-server.com; # e.g., server_name source.example.com;
# root /home/gitlab/gitlab/public;
root /opt/gitlab-4.0/public;
# individual nginx logs for this gitlab vhost
access_log /var/log/nginx/gitlab-access.log;
error_log /var/log/nginx/gitlab-error.log;
location / {
# serve static files from defined root folder;.
# @gitlab is a named location for the upstream fallback, see below
try_files $uri $uri/index.html $uri.html @gitlab;
}
# if a file, which is not found in the root folder is requested,
# then the proxy pass the request to the upsteam (gitlab unicorn)
location @gitlab {
proxy_read_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694
proxy_connect_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://gitlab;
}
} |
| Quote: | 2013/02/25 11:42:01 [crit] 11008#0: *5 connect() to unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket failed (2: No such file or directory) while connecting to upstream, client: x.x.x.x, server: git.my-server.com, request: "GET / HTTP/1.1", upstream: "http://unix:/home/gitlab/gitlab/tmp/sockets/gitlab.socket:/", host: "git.my-server.com:81"
|
The socket path doesn't exists and I don't have any socket file under /opt/gitlab-4.0/ either. Oh... it seems that's because you use unicorn and jirutka recommend to disable it. |
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
| Posted: Mon Feb 25, 2013 2:33 pm Post subject: |
|
|
| edouard.lopez wrote: | | is it possible to use your ebuild without Passenger ? |
Yeah, sure. If you want to use Unicorn instead, just emerge gitlabhq with USE unicorn (enabled by default) and copy /etc/gitlab-4.0/unicorn.rb.example to /etc/gitlab-4.0/unicorn.rb and edit settings.
| edouard.lopez wrote: | | I'm trying to use the native vhost config with the ebuild… |
I don’t understand your configuration. Where is your http://gitlab? There should be some nginx upstream directive. Are you trying to use nginx + Unicorn or nginx + Passenger? |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Fri Mar 01, 2013 7:45 am Post subject: |
|
|
i got 4.2 up tonight through apache + passenger, and conversion from debian / ubuntu install instructions. ruby 1.9.3xxx mysql 5.2 apache 2.2 its very rough on the wiki so far, ill probably have it polished enough for web users in 2 weeks time. as of right now it has database problems in the write up, requires a production database to get up, but it also has entries for dev and test databases, and clients were reporting read/write problems. im giving up for the night though. my biggest problem, was pretty much exactly what spawned this thread...
& the wiki is polished for the most part now |
|
| Back to top |
|
|
ph03
n00b
Joined: 14 Jan 2005
Posts: 39
|
| Posted: Sat Apr 13, 2013 6:54 am Post subject: |
|
|
| BTW: Are there plans to support gitlab 5 with similar ebuilds? Would be glade to help testing! |
|
| Back to top |
|
|
jirutka
n00b
Joined: 17 Feb 2013
Posts: 10
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
