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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2014-03-05 15:25:50 -04:00
commit 96fc3c7edf
14 changed files with 127 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_3_67bfccf0934075559d439b1deafc001e._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnX1msQxnLoSeu7q-i-c9BWghonsN7Qmns"
nickname="Jan Ulrich"
subject="comment 3"
date="2014-03-05T11:47:06Z"
content="""
I observe something similar. Today git-annex started to repair a repository. CPU is at 100%, I can still work because I have a multikernel system, so I'll wait and see if it comes to an end.
"""]]

8
doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
nickname="Jon Ander"
subject="comment 3"
date="2014-03-05T08:10:25Z"
content="""
My connection is pretty fast, I've just copied a 77MB folder through Box's webdav with my file manager in ~90sec and I have never seen a timeout when using my file manager, all uploads finish properly.
"""]]

9
doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.146"
subject="comment 4"
date="2014-03-05T17:11:40Z"
content="""
Previous bug report about this with much more information, please do any followup there:
[[bugs/box.com_never_stops_syncing.]]
"""]]

20
doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="http://grossmeier.net/"
nickname="greg"
subject="comment 5"
date="2014-03-05T04:34:49Z"
content="""
Still seeing it with version 5.20140227
git-annex unused shows 110 keys.
git-annex copy --unused --to $anyremote just returns very quickly without doing anything.
git-annex copy --all --to $anyremote does go through every key and checks.
git-annex copy --key=$some_key_listed_in_unused --to $anyremote also just returns quickly without checking.
I even untrusted the repository via vicfg and passing the --untrust=remote argument.
Again, a direct mode repo that is also assistant'd.
"""]]

8
doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://grossmeier.net/"
nickname="greg"
subject="comment 6"
date="2014-03-05T04:38:26Z"
content="""
Also, in another non-direct/non-assistant'd repo, things work as expected.
"""]]

10
doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.146"
subject="comment 7"
date="2014-03-05T17:08:19Z"
content="""
The only reason copy --key would do nothing is if the key is not locally present in your repository.
Please check if the keys listed by `git annex unused` are present in `.git/annex/objects/`
"""]]

8
doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.146"
subject="comment 3"
date="2014-03-05T16:56:14Z"
content="""
Older versions of git-annex did not preserve more than the very end of the extension when using SHA*E backends, so I guess you added the respective files using two different versions.
"""]]

8
doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawlmOvQXLmGkQAUOIkPBQtsd9d45NqcX80M"
nickname="Jan"
subject="comment 4"
date="2014-03-05T17:07:05Z"
content="""
Ah, so it's a matter of `.JPG.cam` vs `.cam` as an extension -- that makes sense, I do use different versions on these two remotes. Is there some easy way of getting them back to a single underlying content apart from doing that by hand?
"""]]

10
doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.146"
subject="comment 5"
date="2014-03-05T18:02:08Z"
content="""
Well, the easy way, assuming that you don't need the extension in the key at all, is to run `git annex migrate --backend=SHA512 *.cam` in both repositories.
You can also play tricks with `git annex rekey`. I don't know if I'd recommend doing so.
"""]]