mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

respond to all of a user's bug reports at once.. they had copied a repo and so had duplicated annex.uuid

Browse source
This commit is contained in:
Joey Hess 2015-11-30 16:11:45 -04:00
parent 91cbf87180
commit fa7a017b7e
Failed to extract signature
5 changed files with 48 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn
View file

@ -8,6 +8,9 @@ Meanwhile, those files also reside in a remote. git-annex-whereis does show ther
Note that dropping files in current repo (``git annex drop``) and re-getting (``git annex get``) does download the files from that remote. However, a subsequent ``git annext whereis`` again shows 1 copy --- at that remote only.
> Because you have 2 repositories with the same annex.uuid, which is not
> allowed. Fix your misconfigured repo to not have the same annex.uuid and
> that won't happen. [[done]] --[[Joey]]
### What steps will reproduce the problem?

BIN
doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp Normal file
View file

Binary file not shown.

19
doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2015-11-30T19:55:05Z"
content="""
Well, you also filed the bug report
[[Unable_to_take_transfer_lock]], where you said something about having
copied the repository over SMB using `cp` and some kind of OSX copy and
paste.
So, if you did that, it seems likely that you have 2 git repositories with
the same annex.uuid setting. In fact this is confirmed by [another bug
report](http://git-annex.branchable.com/bugs/remote_repo_marked_as___34__here__34__/)
you filed.
Since git-annex expects each repository to have a unique annex.uuid, this
is going to confuse it badly. Don't do that. Use `git clone` to make a clone
of a git repository.
"""]]

8
doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2015-11-30T20:08:10Z"
content="""
@jhannwong you had [2 repos with the same annex.uuid](http://git-annex.branchable.com/bugs/remote_repo_marked_as___34__here__34__)
so if you had the same problem, it was a misconfiguration on your part.
"""]]

18
doc/forum/git_annex_drop_not_freeing_space_on_filesystem/comment_4_368b2c07dc7d98534a77c6153e8486ae._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2015-11-30T20:00:20Z"
content="""
I notice you also filed the bug report
[[bugs/Unable_to_take_transfer_lock]], where you said something about having
copied the repository over SMB using `cp` and some kind of OSX copy and
paste.
So, if you did that, it seems likely that you have 2 git repositories with
the same annex.uuid setting. In fact this is confirmed by [another bug
report](http://git-annex.branchable.com/bugs/remote_repo_marked_as___34__here__34__/) you filed.
Since git-annex expects each repository to have a unique annex.uuid, this is
going to confuse it badly. Don't do that. Use `git clone` to make a clone of
a git repository.
"""]]