StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5041898
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-02-18T13:33:36
FavoriteCount
0
LastActivityDate
2012-04-19T06:13:18.783
LastEditDate
2017-05-23T10:30:59.483
LastEditorUserId
-1
OwnerUserId
6309
ParentId
5041067
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
The <a href="https://stackoverflow.com/users/623049/skipper3k">OP skipper3k</a> <a href="https://stackoverflow.com/questions/5041067/gitolite-git-clone-error/5090221#5090221">reports</a> an issue with <code>RUNTIME_PREFIX</code> in Git, a bit similar to "<a href="https://stackoverflow.com/questions/1465398/git-pull-broken"><code>git pull</code> broken</a>" question: <blockquote> I'm not sure whether <code>RUNTIME_PREFIX</code> is defined for you. But while nosing in the <code>Makefile</code>, I did notice that prefix defaults to <code>$(HOME)</code>. I suspect that this may be the cause of your problems. The simple answer is to put this in <code>~/.bashrc</code>: </blockquote> <pre><code>export GIT_EXEC_PATH=/opt/local/libexec/git-core </code></pre> <blockquote> If you want to find out more about what's going on, you'll probably have to recompile git using <code>port -d upgrade -f git-core</code> (or similar) and look closely at the build log to see where prefix is being set. Incidentally, <code>port cat git-core</code> shows heavy usage of <code>${prefix}</code>. </blockquote> <hr> Original answer: First, did you get the most up-to-date gitolite version? At <a href="https://github.com/sitaramc/gitolite/" rel="nofollow noreferrer">https://github.com/sitaramc/gitolite/</a>, you need to consider the '<code>pu</code>' branch. The <a href="http://sitaramc.github.com/gitolite/install.html" rel="nofollow noreferrer">installation documentation is then this one</a>. <hr> <a href="http://sitaramc.github.com/gitolite/g3why.html" rel="nofollow noreferrer">GitoliteV3 or 'g3'</a> doc: <blockquote> "Installation" consists of the following options: <ol> <li>Keep the sources anywhere and use the full path to run the gitolite command.</li> <li>Keep the sources anywhere and symlink just the gitolite program to some directory on your $PATH.</li> <li>Copy the sources somewhere and use that path to run the gitolite command.</li> </ol> You can run the 'install' command in 3 different ways: </blockquote> <pre><code># option 1 gitolite/install # option 2 gitolite/install -ln # defaults to $HOME/bin, or use a specific directory: gitolite/install -ln /usr/local/bin # option 3 gitolite/install -to /usr/local/gitolite/bin </code></pre> <hr> Old answer for gitolite V2: Second, I prefer the <del>"<a href="https://github.com/sitaramc/gitolite/blob/pu/doc/1-INSTALL.mkd#_from_client_method_install_from_the_client_to_the_server" rel="nofollow noreferrer">from-client method</a>"</del> method: <blockquote> The advantage of this method is that it forces you to solve the ssh pubkey problem before attempting to install. It works best if you have dedicated userids, <ul> <li>one on the server for installing gitolite, </li> <li>and one on the client for administering it.</li> </ul> The disadvantage is that the admin user ends up with two keys <ul> <li>one for shell access (that he started with) and </li> <li>one for gitolite access (which the script creates if needed).</li> </ul> </blockquote> So I like to create a <code>~/.ssh/config</code> file with the two different sets of parameters: <pre><code>host gitolite user git hostname server identityfile ~/.ssh/git host gitadmin user git hostname server identityfile ~/.ssh/id_rsa (myaccount public key) </code></pre> The gitolite-admin is only visible for the first public ssh key: <pre><code>C:\HOMEWARE\git>ssh gitolite hello git, the gitolite version here is v1.5.9-25-ga10287a the gitolite config gives you the following access: R W gitolite-admin @R_ @W_ testing Connection to server closed. </code></pre> With my account: <pre><code>C:\HOMEWARE\git>ssh gitadmin hello myaccount, the gitolite version here is v1.5.9-25-ga10287a the gitolite config gives you the following access: @R_ @W_ testing Connection to mccprdgit10 closed. </code></pre> So: <pre><code>C:\HOMEWARE\git>git clone gitolite:gitolite-admin Cloning into gitolite-admin... remote: Counting objects: 16, done. remote: Compressing objects: 100% (13/13), done. remote: Total 16 (delta 2), reused 0 (delta 0) Receiving objects: 100% (16/16), done. Resolving deltas: 100% (2/2), done. </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGitolite git clone error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.