StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGitolite remembers a repository that it shouldn't
primarykey
Id
6791152
data
AcceptedAnswerId
7043237
AnswerCount
3
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-07-22T14:00:23.297
FavoriteCount
0
LastActivityDate
2011-08-12T16:23:58.577
LastEditDate
2011-08-09T19:51:03.103
LastEditorUserId
178363
OwnerUserId
178363
ParentId
0
PostTypeId
1
Score
1
ViewCount
626
LastEditorDisplayName
text
Body
We have gitolite and it keeps complaining an existing repository doesn't exist. Even after I edited <code>gitolite.conf</code> and removed that repo from the config. So I'm wondering why it 'remembers' that repo? I checked my changes were pushed correctly. The <code>$gituser/.gitolite/conf/gitolite.conf</code> is equal to my local one. The message doesn't come from the <code>gitolite.pm</code> script, the exact error message is <pre><code>remote: fatal: Not a git repository: '/Users/git/repositoires/IJslander.git' </code></pre> For example when committing the gitolite-admin repo: <pre><code>$ git commit -a -m "bogus space" [master 675b4e1] bogus space 1 files changed, 2 insertions(+), 2 deletions(-) $ git push Counting objects: 7, done. Delta compression using up to 2 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (4/4), 360 bytes, done. Total 4 (delta 1), reused 0 (delta 0) remote: fatal: Not a git repository: '/Users/git/repositoires/IJslander.git' To git@redacted.com:gitolite-admin 935c304..675b4e1 master -> master </code></pre> And I have <code>grep</code>ed the whole HDD and nowhere does it mention that repo (but it did mention a new one we tried to make to replace it): <pre><code>~ git$ grep -ilR "IJslander" . 2> /dev/null ./.bash_history ./.gitolite/conf/gitolite.conf ./.gitolite/conf/gitolite.conf-compiled.pm ./.gitolite/logs/gitolite-2011-07.log ./.gitolite/logs/gitolite-2011-08.log </code></pre> And this is from the conf: <pre><code>~ git$ grep -iR "IJslander" .gitolite/conf/gitolite.conf 2> /dev/null repo ijslander-ios //the compiled conf file ~ git$ grep -iR "IJslander" .gitolite/conf/gitolite.conf-compiled.pm 2> /dev/null 'ijslander-ios' => { </code></pre> All repos are under <code>git</code>'s <code>~</code>
Tags
<git><version-control><gitolite><osx-server>
Title
Gitolite remembers a repository that it shouldn't
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USZsub
UserOwnerUserId
1. USZsub
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGitolite remembers a repository that it shouldn't
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POGitolite remembers a repository that it shouldn't
 UserUserId
 USZsub
 VoteTypeVoteTypeId
 VTBountyStart
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.