New answers tagged git
You are right. the MOTD should not be displayed to any user. Gitlab has its own built-in shell that handles users, but that shell is only run when a user logs in with their private key, which isn't working for you. Because logging in as git with a password brings you to a prompt, you should delete the password for git: sudo passwd -d git And then disable ...
Having a look at the blog here I found the solution in one of the comments. Make sure you got the rpmforge repository added to your CentOS (Reference: How to add RPMFORGE repo to CentOS) yum and just run the following command: yum --disablerepo=base,updates --enablerepo=rpmforge-extras install git If you already have git installed then use: yum ...
CentOS supports a "parallel" universe of newer compilers and tools, that doesn't clobber the older versions. You want yum install devtoolset-2 Once it is installed, do scl enable devtoolset-2 bash which will modify your path. You'll have the old version of git in /usr/bin/git, and the newer version in /opt/rh/..../git. The newer one is 1.8.4/. You ...
I hit the same issue on 14.04, however it was a bit more annoying as the package was initializing etckeeper using bazaar automatically on apt-get install. Switching to git in the config file as mentioned above wasn't enough; I first had to undo the bazaar setup which was done at install time, like this: etckeeper uninit The steps above then worked fine.
You need to contact the gitlab developers and obtain an updated package which is compatible with EL7. This is failing because it can't find various bits of upstart which is only present in EL6.
Puppet makes some assumptions about the permissions of some files in /etc/puppet (and the directory itself, I believe). As such, you likely will not be able to make that location writeable to your regular account. This is usually not a good choice anyway. If you want to work in /etc/puppet directly, you should work as root - sudo is an ill fit here. Try ...
On my windows 7 system GitGui looks for the RSA key in the userprofile/.ssh folder or more specifically c:/users/yourusername/.ssh/ The tricky part for my setup was getting the shared host at hostmonster to accept the key. The only way I could get it to work was by using GitGui to create the key pairs (without a password) and then copy and pasting the ...
You're not calling git clone; you're calling sudo which switches to a completely different Unix account (root) and only then calls git clone. The result, as you'd also notice with sudo ssh -v ..., is that ssh is looking for private keys in directories belonging to root, not you. Since sudo cleans the environment by default, ssh cannot use your SSH agent ...
We ended up solving this by using the git user account on that server to host read-only repositories the mirrored the gitlab ones. We then used the gitlab user for running gitlab.
Top 50 recent answers are included