summaryrefslogtreecommitdiff
path: root/doc/bugs/remote_repo_marked_as___34__here__34__.mdwn
blob: bb5da19548b75689075476c076796cfae13c99a4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
### Please describe the problem.

``git annex info`` shows a local repo as "not here" (withou the ``[here]`` tag), and shows a remote repo with the ``[here]`` tag.

I had to manually edit `.git/config` to set my local repo's UUID to the correct one.

> Well, git-annex can only display information that you've told it. 
> In this case you seem to have done something wrong with UUIDs, and so it
> displayed [here] next to the UUID of the local repo, as it's supposed to.
> There's no bug here I think. [[done]] --[[Joey]]

### What steps will reproduce the problem?

I just ``git annex dead`` an old repo, and ``git annex semitrust`` a new repo by the same name as the old repo.


### What version of git-annex are you using? On what operating system?

5.20150731-1build1

Lubuntu 15.10


### Please provide any additional information below.

[[!format sh """
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log


# End of transcript or log.
"""]]

### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)

Yes, lots of luck (need more skill).

git-annex may need more error catches to prevent a wrong order of commands from corrupting a repo. But still, git annex works great.