-
Notifications
You must be signed in to change notification settings - Fork 117
redmine git hosting rugged compiled features ssh red #679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Anyone has been through this?? |
Yes, I'm going through this right now. Nothing works... investigating. |
Following the project's "troubleshooting instructions":http://redmine-git-hosting.io/troubleshooting/#unsupported-url-protocol I have found that a better expression is On Gentoo I had to |
On Debian you need libssh-dev for rugged to build with ssh support. |
As discussed in #732 (comment), issues related to Redmine < 4.0 or severely outdated issues are being closed to help clean up the issue tracker. If this issue is still relevant to you and you are running Redmine >= 4.0, please open a new issue including all new relevant information. |
Thanks a lot! Adding libssh2-dev (on Alpine) saved my day. |
From Redmine 5.0, using rugged 1.5.0.1, you need to build the gem with a specific flag to make it work with SSH:
Cf. https://github.com/libgit2/rugged/pull/928/files I've created #817 to reflect this on http://redmine-git-hosting.io/troubleshooting/ |
Hello,
I finally managed to install the plugin and gitolite, but I still have
ssh
in red for rugged compiled features. Inconfiguration test
everything is in green but this. And inAdministration -> Settings -> Repositories
I have ticked Suversion, Git and Xitolite. All of them have a green tick withsvn
,git
andgit
respectfully. I have seen some other issues where xitolite had an absolute path rather than justgit
.Could the
ssh
being in red and having just 'git´ rather than an absolute path be the problem that I have now? I have been able to create a new repository, but when I check the configuration of the repository, it says that it does not exist in gitolite.Just in case, I can do on the
redmine
user where I installed redmine with bitnami:Searching for the solution I found a closed issue here asking if jbox-gitolite was installed. I did not have this. Therefore, I installed it. Should I have done something else besides
gem install jbox-gitolite
? Should I have ranbundle install
aftergem install jbox-gitolite
?I have seen on another issue here that having ssh red in rugged compiled features can be because rugged/libgit2 has not been compiled with SSH support. So, I followed the
Unsupporterd URL protocol
steps but I still have the issue.Also, if it helps, this is what my
/home/git/.gitolite/conf/gitolite.conf
file looks like:Besides, I
ran gem
update just it case as well.One thing that I have just realized is when I follow this steps to install the
libgit2
library, it says to copy:sudo cp /usr/lib/x86_64-linux-gnu/pkgconfig/libssh2.pc /opt/bitnami/common/lib/pkgconfig/
But as I did not install bitnami redmine with sudo, I copied it to
/home/redmine/redmine-3.3.3-0/common/lib/pkgconfig/
and rather than usingv0.22.2
as suggested, I checkout tov0.25.1
.And one last thing, for step 8 of the
get_started
guideInstall Ruby interpreter for post-receive hook
, rather than doing it with apt-get, I followed these steps:Thanks for the help.
The text was updated successfully, but these errors were encountered: