From fa7a017b7e5d761cd9fe3ff346c90dc5a8702437 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 30 Nov 2015 16:11:45 -0400 Subject: [PATCH] respond to all of a user's bug reports at once.. they had copied a repo and so had duplicated annex.uuid --- ...__44___git-annex-whereis_doesn__39__t.mdwn | 3 +++ ...c5d45bc2ecc95c3c770faa9e22acb._comment.swp | Bin 0 -> 12288 bytes ..._f68c5d45bc2ecc95c3c770faa9e22acb._comment | 19 ++++++++++++++++++ ..._b70e83a44a85b006c2c6105660cd6a7a._comment | 8 ++++++++ ..._368b2c07dc7d98534a77c6153e8486ae._comment | 18 +++++++++++++++++ 5 files changed, 48 insertions(+) create mode 100644 doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp create mode 100644 doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment create mode 100644 doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment create mode 100644 doc/forum/git_annex_drop_not_freeing_space_on_filesystem/comment_4_368b2c07dc7d98534a77c6153e8486ae._comment diff --git a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn index 7381cf7f37..82afb61352 100644 --- a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn +++ b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t.mdwn @@ -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? diff --git a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/.comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment.swp new file mode 100644 index 0000000000000000000000000000000000000000..88ae1a2cc855481f6fd8bcd3e2ee7bb1f858591a GIT binary patch literal 12288 zcmeI2y>1gh5XU#v1W>4vCZl}fEGbb zi+Bbe13Fsr3RKMAIgrpqltFXSUw5}3v;X>Y z5g-CY;9m*&`5JqJn{KQ&ZmjNWf8AHFbRz;pfCvx)B0vO)01+SpM1Tko0U|&It|0*t zGj?{9vHf*4kN^Ll|NcL_&Db~87t}}8JCsFjp}yb3In-CwThuPZ3x; z$0)jp01+SpM1Tko0U|&IhyW2F0{QmHf;uw84mJj53KMEEKkI0ZxOR0f$?qlVxu z%*0fICt(!uqaRZ&oS}&GR&}}qXQ$NL~(Dq$LevP3gbp9<)K%7FepQg zH86N|JI>p~P7T-R*@t?15hu41fjT9y`~2_(3s2!ALofkOivgj4^3@cYH?9j+}VZBm=Md_77*L?{y*gRh_vgu6t J-Yi}i_6vJFMl=8b literal 0 HcmV?d00001 diff --git a/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment new file mode 100644 index 0000000000..344ecfe234 --- /dev/null +++ b/doc/bugs/git-annex-unlock_shows_files___34__here__34____44___git-annex-whereis_doesn__39__t/comment_1_f68c5d45bc2ecc95c3c770faa9e22acb._comment @@ -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. +"""]] diff --git a/doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment b/doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment new file mode 100644 index 0000000000..68e414e53d --- /dev/null +++ b/doc/bugs/whereis_claims_file_is_not_here__44___but_it_is_available_both_here_and_in_another_remote/comment_4_b70e83a44a85b006c2c6105660cd6a7a._comment @@ -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. +"""]] diff --git a/doc/forum/git_annex_drop_not_freeing_space_on_filesystem/comment_4_368b2c07dc7d98534a77c6153e8486ae._comment b/doc/forum/git_annex_drop_not_freeing_space_on_filesystem/comment_4_368b2c07dc7d98534a77c6153e8486ae._comment new file mode 100644 index 0000000000..47e7498c40 --- /dev/null +++ b/doc/forum/git_annex_drop_not_freeing_space_on_filesystem/comment_4_368b2c07dc7d98534a77c6153e8486ae._comment @@ -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. +"""]]